Brian and Wilfried gave the solutions for binary transfers. The thing to remind is that the receiver has to know what data he has to receive: kind and length. For fragmentation, has a look at the document 'tcp/udp primer' available from the support page at my website.
Personnally, I always try to have a line oriented protocol, sending data in ascii instead of binary. This will greatly help interoperability between platforms and languages as data has not always the same binary representation in all languages and platforms. Most well known TCP/IP protocol use line oriented ascii protocols, even for HTTP and FTP where there is also binary data. -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Igor Pokorny" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Monday, August 15, 2005 12:50 AM Subject: [twsocket] Twsocketserver > Hi guys, > > I do have a realtime application communicates to one side by USB and to > the other acts as http server and/or TCPserver. I am trying to use ICS > http server and everything seems OK. I use another free component of TCP > server that has to run in different thread because of not event driven. > Synchronizing makes me a lot of problems so I decided to use TCP > server from ICS. My TCP communication isn't line oriented. Could I find > any documentation to Twsocketserver or some example how to handle binary > and maybe fragmented packets? I am already late with my project so I > would prefer quick, maybe dirty help :-( > > Thanks in advance > > Igor > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be