On Tue, Sep 16, 2008 at 2:43 PM, Pavel Ivanov <[EMAIL PROTECTED]> wrote:
> > I guess it's JavaScript in Glassfish Management Console that works > properly only in IE and causes site session to timeout. How come a js function causes a session timeout ?! It should be the other way around, if there is some js code the polls the server, then it won't timeout. > In Chrome it > doesn't work good for some reason and thus session never timeouts. :) > > On Tue, Sep 16, 2008 at 5:29 AM, Dewin Cymraeg <[EMAIL PROTECTED]> > wrote: > > > > It seems to me that this isn't necessarily desired behaviour from the > > browser. It should be up to the web-application itself to make this > > kind of decision (whether to ping using AJAX, e.g.) rather than the > > browser's responsibility. > > > > It would be interesting to put something like TcpMon in the middle to > > see if there really is any additional, browser-generated traffic. > > > > Another possibility is that the JavaScript in the web-application is > > firing as required in Chrome, but isn't working properly in IE7. That > > is, it may be a bug in the Glassfish Management Console which exhibits > > different behaviour for IE7. Maybe you could try it using Firefox too? > > > > Rhys > > > > > > On Sep 16, 4:41 am, eran <[EMAIL PROTECTED]> wrote: > >> I use a certain application server (Glassfish) for development, and > >> have its management console (which is a web site) opened in my browser > >> all the time. Till Chrome, using IE7 I had to login after a few > >> minutes of inactivity, which was quite annoying. Using Chrome, I can > >> leave the site untouched for hours and even days, and them go back to > >> using it without any need to login. > >> > >> What I suspect Chrome does is somehow ping the web server > >> occasionally, thus keeping the session alive and preventing it from > >> timing out. But this is just a guess; there might be some other way. > >> Any ideas? > >> > >> BTW, this behavior settles well with the vision of using the browser > >> as a web-OS. On your desktop, applications almost never timeout and > >> lock. This is great, though it might effect sites by forcing them to > >> store a larger number of opened session than they used to. > > > > > > > > > -- Regards, Youssef --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" 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/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
