-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wilfried Mestdagh wrote: >>Again, as I've seen in archive here before, what happens if my >>information gets processed in two batches (packets)? When do I decide >>OK, enough is enough, and continue on processing? Is TWSocket >>neccessarily fit for binary-type protocols like Napster/ICQ/WASTE/etc >>with variable-length packets? > > > Sorry I dont understeand what you asking here. You can send binary data > of course but if you wants to use LineMode then you have to escape some > bytes, otherwise you have to send some length byte/word/dword. >
I guess what I'm trying to say is that with a conventional program, you can initiate a send, then for example if you receive a certain packet type, read more for one operation (say receiving a file listing after asking the server for it) and then keep your program going. For me it is difficult to understand how to "packetize" a TCP stream and rebuild packets on the receiving side, and only read what I think is neccessary for a certain programmer-defined packet type (and then act on them) when not using LineMode and using the *event-driven model* ICS employs. It's easy with LineMode on - ICS only forwards the data on when it receives a delimeter. But when it's off, it seems as though anything other than file sends and receives (because you don't really act on the file stream, you just send or recieve its bytes) proves to be a difficult task. Can you share some insight? Cheers, Wes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCnhriB5TesQcz1CoRAlapAKC+QMRApKtc7QvUFT+97gXTHQc+lQCggJWZ 6EHgR/41vE9lCLit6LQY2yg= =Hetw -----END PGP SIGNATURE----- -- 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
