It would be helpful, for validation, if the Message object could expose information regarding the underlying data read from the Mesh API
It would be good to know the 'raw bytes read' (before any transparent decompression is applied) and also the 'bytes read' (being the decompressed size served to the consumer reading / iterating the underlying message content.
It would be helpful, for validation, if the Message object could expose information regarding the underlying data read from the Mesh API
It would be good to know the 'raw bytes read' (before any transparent decompression is applied) and also the 'bytes read' (being the decompressed size served to the consumer reading / iterating the underlying message content.