Yes, using HTTP/1.1 you have perstant connexions. See Keep-Alive in the
source code.
That's what I'm using, but it's not the same.
When I post a stream (10k as test) to the server which then sends it to the
other computer, it's about 90 times faster then sending 1000
"10byte"-strings.
of couse, there's a little overhead this way, although the "head" part is
almost empty.
After sending a string, there is a diconnect, even with keep-alive and I can
see a 30 ms latency (to the US) for each request.
It's the nature of http (google is working on a new implementation that
doesn't have this limit, but this can take years before it's accecpted).
Normally, this 30ms latency isn't a problem, but for this application, it is
and I need a different approach.
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
