I'm impressed. The imbalance between encoding and decoding speeds seems a useful strategy when you are building special purpose hardware and software applications.
It seems if you're making a central source of data that is able to tolerate a much slower write process versus a quick read process that this approach can be advantageous.
Maybe using this core method in a problem space which maps to the radio/signal broadcast process of many receivers but a central source of truth.
I can imagine if you had an information base that changed slowly or which was pre-processed in a batch fashion, that it could use this method.
It doesn't even need for the central data to be decoded into a graphical image.
I think this radio model could map the problem space for a centralized system that maintained a list of items and their prices which needed to be broadcast to the retail outlets on a regular basis.
Or a common cache storage to make some complex data manipulation calculations centrally performed available to a large number of satellites who just need the end results but do not have the need to do local calculation.
I think this radio model could map the problem space for a centralized system that maintained a list of items and their prices which needed to be broadcast to the retail outlets on a regular basis.
Or a common cache storage to make some complex data manipulation calculations centrally performed available to a large number of satellites who just need the end results but do not have the need to do local calculation.