The timeout is for the max time the app server gets to respond. If it closes the connection earlier (which it should do, once it sends its response), then the delay is shorter. This is what long polling is all about. So if you set the delay to 15 seconds, it doesn't mean you have to wait for 15 seconds every time. That's only, when the server doesn't send the response within 15 seconds.
But as dablack says, probably mod_jk is the better solution anyway. However, like I said earlier, there may be additional proxies between your server and the client. So if it doesn't work correctly with mod_proxy, this could indicate, that there is some problem in the way the app server and the client interact. I have the feeling, that the server maybe doesn't close its connection, so the proxy won't (always) flush its contents. This triggers a timeout on the proxy or on the client (depending on which is shorter). On Feb 20, 2:08 am, Fran <[email protected]> wrote: > If I dont put a short timeout, the aplication isnt good. > Do you imagine that the MSN Messenger delay 15 seconds to show you the > contact list? > > I need that the solution works as the aplication in tomcat. If I > execute the aplication on tomcat, it work without timeout. So I need > when the aplication works in apache, seems that is working in tomcat. > > Im going to show the url that you tell me. Thanks! > > On 20 feb, 01:57, Chris Lercher <[email protected]> wrote: > > > > > BTW, here's a link about timeouts + > > Comet:http://code.google.com/p/google-web-toolkit-incubator/wiki/ServerPushFAQ -- 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.
