I'm testing an application that has to control a remote machine.
The communication goes through an intermediate http server that connects 2
http clients.
A--Server--B-machine
computer A controls computer B wich controls the machine.
When computer B is located in the US, some message aren't
I'm testing an application that has to control a remote machine.
The communication goes through an intermediate http server that connects 2
http clients.
A--Server--B-machine
computer A controls computer B wich controls the machine.
When computer B is located in the US, some message aren't
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,
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,
I don't agree with you. HTTP protocol has all support for real keep alive
connections. request can even be sent before the previous answer has been
received.
BUT most commercial webserver do break the connection very quickly.
Probably to be able to support a large number of clients. If you
I don't agree with you. HTTP protocol has all support for real keep alive
connections. request can even be sent before the previous answer has been
received.
BUT most commercial webserver do break the connection very quickly.
Probably to be able to support a large number of clients. If you
Well, proxies may also break the connections.
Never had problems with that, but new requests are delayed somehow.
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
