> This is not exactly the answer for my question. Maybe it was the answer for the question, but the question was not exactly what you intened :-))
> Think of coding the Picture-Data in just readable Ascii-Characters. This > maybe result in a very large string, ended with #13#10. I thought this > result in a single OnDataAvailable-Event where I can read the whole string > with one call to receivestr. I thought TWSocket concats the single parts > until it finds the #13#10 (in linemode of course) and fires a single > onDataAvailable-Event. > > Am I wrong? You are right. > Naturally this is not a good approach - sending it binary with a special > data-structure is much better. Depends of many factors but yes at first glance it is not a high performance solution. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) 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
