subes
commented
2 years ago This will then be used to allow arbitrary schema values inside the master/slave communication of the historical resolver. Currently the maximum message size should be calculated from 1000 bars, though level2 data might have a variable size that can not be calculated in a guaranteed way, instead fragmenting needs to be used to handle that kind of data.
This can be used with limited size channels like MappedMemory to transmit large messages in multiple chunks as limited by the internal channel implementation. The maximum size to fragment on needs to be provided as a constructor argument. This should work with CommandMessages using a separate sequence number. The command messages with its own sequence becomes just a payload for the FragmentingChannel. So it does not need to know about the existence of an outer sequence.