> SendBlock looks nice, it kinda allows guaranteed-packet-delivery > communication style. Especially nice if it's optimized for minimal > overhead. But after looking at the source I found that it has more of > a clean but not very optimal implementation:
Previous version was optimal an not doing reallocations. But it is not optimal for sending through wire. (Classic 200ms delay problem...) So, I made quick fix to current routine. It is not optimal due reallocations (what can be a problem on very huge payload only), but it avoid this 200ms delay problem. What is a problem? You need to send lenght and data by one send call. Have you idea how to do it without reallocation? (Some kind of output buffering not solve this - it just hide reallocation to buffer manipulation routine.) -- Lukas Gebauer. E-mail: gebau...@mlp.cz http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
