Thursday, January 27, 2011

Re: Persistent HTTP Connection

Try this:
http://download.oracle.com/javase/1.5.0/docs/guide/net/http-keepalive.html

and this:

http://www.io.com/~maus/HttpKeepAlive.html

The salient points are:

0. 'Keep Alive' is really a connection cache.
1. 'Keep Alive' is default on Http 1.1 (and who remembers 1.0?)
2. 'Keep Alive' is basically a way that the server caches the connections for re-use to the client - the operative word is cache. An idle connection will be painlessly recycled for you.
3.There is no specific Keep-Alive timeout - see 2. above.


Typically a given server can support 100+ connections - on Tomcat its a configuration setting - it probably is in all the other app-servers (or at least it should be...) - an 'active' connection is one that actually has data travelling across it, in one direction or another. A modern, high capacity machine can support many more.


HTH

Alan



On 1/27/2011 1:59 PM, Richi Plana wrote:


On Thu, Jan 27, 2011 at 2:38 PM, Thomas Broyer <t.broyer@gmail.com> wrote:

That's HTTP: a request and a response, within a single TCP connection (and using pipelining and/or keep-alive, you could send multiple requests and receive their responses all in a single TCP connection).
The fact that it's asynchronous from your point of view (the code) is a different thing.


This is what I meant by "keeping the persistent connection open". If multiple requests go on the same TCP connection, how long is it kept alive? How many operations go over it before it is disconnected? My concern is that a GWT application might require a persistent TCP connection with the app server to the point that it hits a system maximum is users leave their application on even though no activity is taking place.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.


No comments:

Post a Comment