On Thu, Jan 27, 2011 at 2:38 PM, Thomas Broyer <[email protected]> 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
