[Seaside-dev] Re: [Seaside Commits] Seaside 3.0: Seaside-Core-jf.682.mcz

[Dale Henrichs]

I believe that the only concern that I had was that the cache instance 
variable wasn't going to be set in the 
WANoReapingStrategy/WANullReapingStrategy case so I didn't want #reap to 
be sent which would result in a MNU ... I didn't spend a lot of time 
trying to figure out who might be sending reap, but the way it was 
implemented it certainly looked like reap could/should be sent and I 
didn't want that to happen....ever...

Dale

On 01/04/2011 11:48 AM, Philippe Marschall wrote:
> 2011/1/4 Dale Henrichs<dhenrich at vmware.com>:
>> GLASS doesn't reap sessions using the normal Seaside mechanism, so I created
>> a WANoReapingStrategy class that did nothing and then modified the code in
>> WACache to use that as the reaping strategy.
>>
>> GLASS runs with multiple vms and those vms are all sharing the session
>> state, so it doesn't make sense to try to coordinate session reaping across
>> multiple vms ... it is easier to run a separate vm that does the session
>> reaping (once a minute by default) ...
>
> Yeah, we get that. The question at least the way I understood it
> couldn't you just use the plain WACacheReapingStrategy instead of
> WANoReapingStrategy/WANullReapingStrategy?
>
> Cheers
> Philippe