Re: Sessions and keep-alives
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]
Re: Sessions and keep-alives
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. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Fri, May 13, 2005 12:04 pm, Tim Diggins said: > I'd just include this invisible gif on every page (request) of webapp B. > (bone-headed solution, but why get more tricksy until you need it). > > -- Tim > > Patrick Lacson wrote: >> Interesting solution Tim.. so webapp B would invoke this invisible gif >> from webapp A on an interval basis? >> >> -P >> >> On 5/13/05, Tim Diggins <[EMAIL PROTECTED]> wrote: >> >>>Hi Patrick - >>> >>>If not an iframe, why not a gif... There's nothing (in principle I >>>think*) stopping you having a jsp page that returns a (tiny, invisible) >>>gif (with the right mimetype) and with appropriate expires/cache-control >>>headers to make sure that it gets "got" each time. That's the way some >>>web-counters work, for example, and I can't see it would create a >>>problem... (I don't however know whether you can maintain two session >>>cookies at the same time... Would work however with a param-based >>> session). >>> >>>--Tim >>> >>>* I have done this in similar kinds of situations with python & php, but >>>not tomcat. >>> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
I'd just include this invisible gif on every page (request) of webapp B. (bone-headed solution, but why get more tricksy until you need it). -- Tim Patrick Lacson wrote: Interesting solution Tim.. so webapp B would invoke this invisible gif from webapp A on an interval basis? -P On 5/13/05, Tim Diggins <[EMAIL PROTECTED]> wrote: Hi Patrick - If not an iframe, why not a gif... There's nothing (in principle I think*) stopping you having a jsp page that returns a (tiny, invisible) gif (with the right mimetype) and with appropriate expires/cache-control headers to make sure that it gets "got" each time. That's the way some web-counters work, for example, and I can't see it would create a problem... (I don't however know whether you can maintain two session cookies at the same time... Would work however with a param-based session). --Tim * I have done this in similar kinds of situations with python & php, but not tomcat. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
Interesting solution Tim.. so webapp B would invoke this invisible gif from webapp A on an interval basis? -P On 5/13/05, Tim Diggins <[EMAIL PROTECTED]> wrote: > Hi Patrick - > > If not an iframe, why not a gif... There's nothing (in principle I > think*) stopping you having a jsp page that returns a (tiny, invisible) > gif (with the right mimetype) and with appropriate expires/cache-control > headers to make sure that it gets "got" each time. That's the way some > web-counters work, for example, and I can't see it would create a > problem... (I don't however know whether you can maintain two session > cookies at the same time... Would work however with a param-based session). > > --Tim > > * I have done this in similar kinds of situations with python & php, but > not tomcat. > > Patrick Lacson wrote: > > I've considered iframes, but unfortunately not an option for us. > > > >>From what I understand AJAX can make async calls to the HTTP server > > from the webapplication only, not on behalf of another. So if the > > popup application is webapp B, and the parent webapp A, how can I call > > the webapp A server from webapp B for the keep-alive? > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
Hi Patrick - If not an iframe, why not a gif... There's nothing (in principle I think*) stopping you having a jsp page that returns a (tiny, invisible) gif (with the right mimetype) and with appropriate expires/cache-control headers to make sure that it gets "got" each time. That's the way some web-counters work, for example, and I can't see it would create a problem... (I don't however know whether you can maintain two session cookies at the same time... Would work however with a param-based session). --Tim * I have done this in similar kinds of situations with python & php, but not tomcat. Patrick Lacson wrote: I've considered iframes, but unfortunately not an option for us. From what I understand AJAX can make async calls to the HTTP server from the webapplication only, not on behalf of another. So if the popup application is webapp B, and the parent webapp A, how can I call the webapp A server from webapp B for the keep-alive? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Sessions and keep-alives
Wen launching webapp B (from A), you can pass jsessionid as url parameter (not as jsessionid) to B; with this jsessionid you can call A from B for keep-alive. Gernot -Ursprüngliche Nachricht- Von: Patrick Lacson [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 13. Mai 2005 06:57 An: Tomcat Users List Betreff: Re: Sessions and keep-alives I've considered iframes, but unfortunately not an option for us. >From what I understand AJAX can make async calls to the HTTP server from the webapplication only, not on behalf of another. So if the popup application is webapp B, and the parent webapp A, how can I call the webapp A server from webapp B for the keep-alive? On 5/12/05, Tim Funk <[EMAIL PROTECTED]> wrote: > The simplest kludge is an iframe that is "hidden" and uses a META refresh. > > Or look at using ajax. > > -Tim > > Patrick Lacson wrote: > > > hi All! > > > > I'm involved in a project that integrates two disparate web > > applications: webapp A is using WebSphere and webapp B is using > > Tomcat. > > > > The integration involves Single Sign On, with webapp A being the > > primary webapp from which webapp B is launched. webapp B is launched > > as a popup-window. > > > > My question is: how can i ensure that while the user is working on the > > webapp B popup, the parent window webapp A, does not time-out? > > > > Thanks in advance! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
If you can use Javascript (and can require it), what you could do is set a timer in app B's onLoad event to call a Javascript function in app A from app B (parent.myFunction();)... This function could refresh whatever the current page is in some interval less than your timeout period. You'll have to ensure all pages of app A have that refresh function in page-scope, and that all pages in B set that timer and make the call. If a full-page refresh isn't feasible, you can make an AJAX call to app A that does really nothing, but that should be enough to keep the session from timing out. Does that all make sense? (I'm not sure I described it well) Frank W. Zammetti -Original Message- From: "Patrick Lacson"<[EMAIL PROTECTED]> Sent: 5/13/05 12:56:43 AM To: "Tomcat Users List" Subject: Re: Sessions and keep-alives I've considered iframes, but unfortunately not an option for us. >From what I understand AJAX can make async calls to the HTTP server from the webapplication only, not on behalf of another. So if the popup application is webapp B, and the parent webapp A, how can I call the webapp A server from webapp B for the keep-alive? On 5/12/05, Tim Funk <[EMAIL PROTECTED]> wrote: > The simplest kludge is an iframe that is "hidden" and uses a META refresh. > > Or look at using ajax. > > -Tim > > Patrick Lacson wrote: > > > hi All! > > > > I'm involved in a project that integrates two disparate web > > applications: webapp A is using WebSphere and webapp B is using > > Tomcat. > > > > The integration involves Single Sign On, with webapp A being the > > primary webapp from which webapp B is launched. webapp B is launched > > as a popup-window. > > > > My question is: how can i ensure that while the user is working on the > > webapp B popup, the parent window webapp A, does not time-out? > > > > Thanks in advance! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] [Message truncated. Tap Edit->Mark for Download to get remaining portion.] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
If you can use Javascript (and can require it), what you could do is set a timer in app B's onLoad event to call a Javascript function in app A from app B (parent.myFunction();)... This function could refresh whatever the current page is in some interval less than your timeout period. You'll have to ensure all pages of app A have that refresh function in page-scope, and that all pages in B set that timer and make the call. If a full-page refresh isn't feasible, you can make an AJAX call to app A that does really nothing, but that should be enough to keep the session from timing out. Does that all make sense? (I'm not sure I described it well) Frank W. Zammetti -Original Message- From: "Patrick Lacson"<[EMAIL PROTECTED]> Sent: 5/13/05 12:56:43 AM To: "Tomcat Users List" Subject: Re: Sessions and keep-alives I've considered iframes, but unfortunately not an option for us. >From what I understand AJAX can make async calls to the HTTP server from the webapplication only, not on behalf of another. So if the popup application is webapp B, and the parent webapp A, how can I call the webapp A server from webapp B for the keep-alive? On 5/12/05, Tim Funk <[EMAIL PROTECTED]> wrote: > The simplest kludge is an iframe that is "hidden" and uses a META refresh. > > Or look at using ajax. > > -Tim > > Patrick Lacson wrote: > > > hi All! > > > > I'm involved in a project that integrates two disparate web > > applications: webapp A is using WebSphere and webapp B is using > > Tomcat. > > > > The integration involves Single Sign On, with webapp A being the > > primary webapp from which webapp B is launched. webapp B is launched > > as a popup-window. > > > > My question is: how can i ensure that while the user is working on the > > webapp B popup, the parent window webapp A, does not time-out? > > > > Thanks in advance! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] [Message truncated. Tap Edit->Mark for Download to get remaining portion.] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
I've considered iframes, but unfortunately not an option for us. >From what I understand AJAX can make async calls to the HTTP server from the webapplication only, not on behalf of another. So if the popup application is webapp B, and the parent webapp A, how can I call the webapp A server from webapp B for the keep-alive? On 5/12/05, Tim Funk <[EMAIL PROTECTED]> wrote: > The simplest kludge is an iframe that is "hidden" and uses a META refresh. > > Or look at using ajax. > > -Tim > > Patrick Lacson wrote: > > > hi All! > > > > I'm involved in a project that integrates two disparate web > > applications: webapp A is using WebSphere and webapp B is using > > Tomcat. > > > > The integration involves Single Sign On, with webapp A being the > > primary webapp from which webapp B is launched. webapp B is launched > > as a popup-window. > > > > My question is: how can i ensure that while the user is working on the > > webapp B popup, the parent window webapp A, does not time-out? > > > > Thanks in advance! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sessions and keep-alives
The simplest kludge is an iframe that is "hidden" and uses a META refresh. Or look at using ajax. -Tim Patrick Lacson wrote: hi All! I'm involved in a project that integrates two disparate web applications: webapp A is using WebSphere and webapp B is using Tomcat. The integration involves Single Sign On, with webapp A being the primary webapp from which webapp B is launched. webapp B is launched as a popup-window. My question is: how can i ensure that while the user is working on the webapp B popup, the parent window webapp A, does not time-out? Thanks in advance! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sessions and keep-alives
hi All! I'm involved in a project that integrates two disparate web applications: webapp A is using WebSphere and webapp B is using Tomcat. The integration involves Single Sign On, with webapp A being the primary webapp from which webapp B is launched. webapp B is launched as a popup-window. My question is: how can i ensure that while the user is working on the webapp B popup, the parent window webapp A, does not time-out? Thanks in advance! -- Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
