Well, unless I misunderstood, the requirement is to keep the session for
webappA alive as long as the session for webappB is alive, so if webappB
is to be alive, then it must have new pages from the server (no need for
a refresh there. Then the webappB's pages (views) could include a
reference to the (uncachable) gif which will be on the webappA's site
(and which will require, and thus keep alive, a session). On the other
hand, this might engender some kind of coupling between the two webapps,
so maybe not the best solution (the whole thing doesn't feel like "the
best solution"), but one __could__ get around this by passing in some
optional parameter giving the url of the gif that needs to be included
on every page, thus decoupling the two apps.
Anyway, I may well have totally misunderstood the situation, so
probably, nuff said on the area.
Frank W. Zammetti wrote:
I'm curious how this would work? If I open a page with an invisible GIF,
there's no way (without scripting and such) to have the GIF "refresh",
right? Or is there something I'm missing?
You can set a meta refresh on the page, but not the GIF itself, as far as
I know anyway.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
