In a previous email it was mentioned that Resin threw an error when logging out, however, tomcat didn't. I did a quick lookup at caucho and found
http://www.caucho.com/support/resin-interest/0207/0332.html my guess is that Tomcat wrote a workaround for this behavior, but Resin sticks to the contract/implementations provided. I could be wrong:) timo On 11/30/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > On Wed, November 30, 2005 1:31 am, Andreas Ernst said: > > Error in lobbyUpdateHandler() - 411 > > after entering a room > > listUsersInRoomHandler() - 411 > > Hmm, that's weird... I'm not sure if that's an HTTP error or something > from XMLHttpRequest... if it's HTTP, that's a server rejection because no > Content-Length was sent by the client, which might be possible here, but > it seems a bit unlikely. I'll have to see if I can find any meaning for > that code as far as XMLHttpRequest goes. > > Woah, hold on... are you absolutely sure it says "Error in > lobbyUpdateHandler()" and not "Error in lobbyUpdateStatsHandler()"? I ask > because the string "Error in lobbyUpdateHandler()" doesn't appear in the > code, but "Error in lobbyUpdateStatsHandler()" does... if what you say is > really what you see, then this might be another Resin issue (every bug I > have on my list is because of running it in Resin for the demo, I don't > see the same problems in Tomcat). > > > pls no TOFU ;-) > > I had to look that up, I've never heard that one before :) > > Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
