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?
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). Please just correct me if I am wrong. -- Richi -- 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.
