> I understand you, but the problem is that the paint process in Receive > machine must paint at the same time that the paint process in the Sent > machine. > Here is the central point because the UDP protocol is asyncronous and I > need two process in the same time in both machines.
Why not having a queue at the receiving computer that hold everything that has to be painted. If you persist with UDP, then you must implement yourself an error detection and correction mechanism (that is somewhat reinventing TCP). TCP is very fast when it comes to streaming. It's a windowed protocol that works very well. You will not gain much speed with UDP in most cases. And as I understand, you are not in the case where you can gain speed. If TCP is slow for you, it is probably because you have bad network and a lot of retries for error correction. Using UDP and your own error detection and correction protocol would probably result in even less performance. Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] The author for the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) 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
