[Seaside] How to configure session timeouts (age)
Sven Van Caekenberghe
sven at stfx.eu
Wed Nov 30 17:20:49 UTC 2016
> On 30 Nov 2016, at 17:36, Petr Fischer <petr.fischer at me.com> wrote:
>
> 1) Pharo 5.0 with latest stable Seaside 3.2 on my side.
>
> 2) No "expiryPolicy" in WACache class (no expiryPolicy method at all in whole image) - I need to browse a ton of Seaside internal classes again and try to find more (documentation/book is IMHO outdated)...
Apparently caching got seriously refactored between 3.1 and 3.2
https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog
Others might be better suited to help you, this is the first time I see these changes
> 3) Spotter has nice modern flat UI, even tooltips are "polished", a lot of details and great functionality (I know how hard is to make a perfect GUI, a lot of work) - but when I use Spotter sometimes, near 10 windows with SubscriptOutOfBounds appears on the screen... I really hate closing this exception windows... I need to find more and post a bugreport somewhere...
That is not normal. Yes, you need to file good bug reports.
> pf
>
>
>> What Pharo version are you on?
>> I am using Pharo 4.0 with Seaside 3.1.
>> The method is WACache>>#expiryPolicy
>>
>> BTW, you should use Spotter (Shift-Enter) for all your searching ;-)
>>
>>> On 30 Nov 2016, at 16:32, Petr Fischer <petr.fischer at me.com> wrote:
>>>
>>> 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 <petr.fischer at me.com> 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
>>>>> seaside at lists.squeakfoundation.org
>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mariano
>>>> http://marianopeck.wordpress.com
>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
More information about the seaside
mailing list