On Thursday, January 27, 2011 10:11:52 PM UTC+1, richip wrote: > > I just assumed that GWT required a persistent HTTP connection when I read > that it handles RPC calls asynchronously. Otherwise how would the server > know where to contact the browser at? Am I right in thinking that the > asynchronous response to an RPC call is sent back over the same HTTP session > and is torn down immediately after? >
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. > Another reason I thought that a persistent connection was required was > because the browser client seemed to know immediately as soon as the Jetty > application server went down, but I guess this is just a special scenario > when running the browser client in debug mode (some plugin in IE, I > believe). > The DevMode plugin indeed uses a "persistent TCP connection", but that's a different kind of connection: it talks its own protocol their, not HTTP. -- 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.
