> Other way is to reserve the sync char and use an escape sequence when > you intend to send a databyte with the sync value. More overhead for > some values in the datastream, but an effective way to keep sync and > quickly recover when sync is lost. SLIP is an example of this.
Thanks, I'll check out SLIP: http://tools.ietf.org/html/rfc1055 Looks like this needs a library. > And for error checking: checksums (and xor) of data give some > assurance, but I would not call them reliable. CRC of 16 bits or more > are much better. There are many examples on the of CRC16-CITT and > others on the net. Depends how much data you are transferring. If you are only sending 2 bytes, an xor should be sufficient. Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
