Why don't you use the algorithm logic in HTTP and explicitly state how many
bytes will follow in a header? for example this is how it is done in chunked
encoding in HTTP (pseudo code):

<10 bytes of data>
<20 bytes of data>
<end of stream>

And an extra first record item, present in all records, used to identify the record type.

But this is not a communications problem. If you are able to save your data to a file, and later load it reconstructing your records, use the same schema to send it (same as save to a file) and receive it (same as load it from a file)

To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to