[Seaside] Multiple Browser Tabs on Same Application

Philippe Marschall philippe.marschall at gmail.com
Fri Dec 4 05:58:05 UTC 2009

2009/12/4 Ken Treis <ken at miriamtech.com>:
> On Dec 3, 2009, at 1:24 PM, Philippe Marschall wrote:
>>> 1. Use the Ramon/Lukas Ajax "ping" [1] to keep the page alive. We're already doing this to keep sessions alive, but we could ramp up its frequency. Downside is a lot of extra chatter between the browser and the server over the life of the session.
>> I don't think this solves your problem. Keep in mind that the ping
>> works together with the session timeout. If you session timeout is 30
>> min you should ping about every 25min or so. More frequently doesn't
>> change anything.
> That's interesting. Doesn't the ping update the the age table in cache, thus making sure that the continuation stays around? It seems like one ping per tab would keep each tab's original rendering context continuation alive. The ping would have to run more frequently to be useful in this regard, but then it would serve two purposes -- keeping the session alive, and keeping the continuation for that page near the top of the cache.
> Or am I missing something?

No, you're right. But then there would be a "gap" in the continuations
stored between the new and the old tab. They'll no longer be able to
use back button all the way to the old tab, some of those pages will
still display a session expired. Your users are using the back button
more often than the default settings anticipated so I'd change the


More information about the seaside mailing list