On 04/02/12 14:14, Bernd wrote:
2012/2/4 Bernd:
You need a robust way to determine how long your
protocol message is, at which byte exactly it ends and the next
message begins.
The simplest way would probably be if you prepend all your messages
with a length field and a checksum field to be sen
2012/2/4 Bernd :
> You need a robust way to determine how long your
> protocol message is, at which byte exactly it ends and the next
> message begins.
The simplest way would probably be if you prepend all your messages
with a length field and a checksum field to be sent as the very first
bytes of
2012/2/1 Malcolm Poole :
> Before I set out to implement the procedures to do this myself, can someone
> reassure me that this needs to be done and that I am not re-inventing the
> wheel?
The TCP protocol will transparently split the data into the packets of
needed size without user intervention,
I'm working on a client/server project which involves sending SQL
commands from server to client and vice versa.
I've been using the LTCP component for both the client and the server,
which have been working perfectly during testing on the same machine and
between different virtual machines, s
