Re: How to configure session timeouts (age)

What Seaside version do you use? Are you on Pharo?

By Pharo method Finder, there is no method "expiryPolicy" at all (in whole image).

Thanks! pf


> This is the way I do it and it works for me:
> 
> app cache expiryPolicy configuration
>         at: #'cacheTimeout'
>         put: 5 hours asSeconds
> 
> That should go in the code you use to register your seaside app (likely
> from a class side #initialize).
> 
> Let me know if that helped.
> 
> Cheers,
> 
> On Sat, Nov 26, 2016 at 5:22 PM, Petr Fischer <[email protected]> wrote:
> 
> > Hello, when starting my image with Seaside app, I have this code in
> > startup method:
> >
> > -----
> > WAMySeasideApp>>startUp: resuming
> >         WAMySeasideApp waApplication
> >                 preferenceAt: #maximumRelativeAge
> >                 put: 18000. "5 hours"
> >         WAEFTTasksApp waApplication
> >                 preferenceAt: #maximumAbsoluteAge
> >                 put: 86400. "24 hours"
> >         ZnZincServerAdaptor startOn: 8080.
> >
> > WAMySeasideApp>>waApplication
> >         ^ WAAdmin defaultDispatcher handlerAt: 'my-seaside-app'
> > -----
> >
> > This "maximum age" session parameters are correctly showing in seaside
> > config web app, but every seaside session is still 30 minutes.
> >
> > What is proper way to configure session timeouts (age), dynamically, via
> > code?
> >
> > Thanks, pf
> > _______________________________________________
> > seaside mailing list
> > [email protected]
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> >
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com

> _______________________________________________
> seaside mailing list
> [email protected]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside