Hi David, A portal application and portlet applications are also web applications. So the servlet container is in charge of managing timeout sessions of each web application. Regarding the session lifecycle management, Jetspeed could synchronize session invalidations of portal application and portlet applications. (See PLT.18.4 of the Portlet Spec.) However, this doesn't mean the management of session timeout of each portlet application.
Regards, Woonsan ----- Original Message ---- > From: David Just <[email protected]> > To: Jetspeed Users List <[email protected]> > Sent: Tue, July 13, 2010 7:38:53 AM > Subject: Are session timouts on a portlet by portlet basis? > > Hi, > > > > I'm working on a portal that is meant to stay up and running thought the > day after signing in, even when no interaction is going on. The portal > / portlet is updated periodicly using an AJAX call that hits a custom > Jetspeed AJAX service. It seems that Jetspeed's session stays live > correctly, but individual portlets seem to be timing out if the user > doesn't interact with them frequently enough. Is Jetspeed in charge of > the sessions for the portlets or do I have to write keep-alive AJAX to > keep my portlets up and running? > > > > > > > > David Just l Senior Software Engineer l Vision Solutions l +1 (507) 529-5939 > l >[email protected] > The contents of this e-mail (and any attachments) are privileged and >confidential. Unauthorized use is strictly prohibited. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
