<div dir="ltr"><div><div><div>ive tried WASession allInstances do: [ : item | item unregister].<br></div>and various other permutations.<br><br></div>Some sessions go away, but most do not. So something else is hanging onto the sessions. Eventually I will get fed up with my bloated image and reload everything from source.<br>
<br></div>If there is a reasonable way to track what is holding onto the sessions i can track that down and either fix my own bugs, or submit a new one here to the list.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Feb 26, 2014 at 10:00 AM, Bob Arning <span dir="ltr"><<a href="mailto:arning315@comcast.net" target="_blank">arning315@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font face="Georgia">Umm, my reply was to Jon Paynter's message
which was basically how to clean up during development. Whether
someone finds some applicability to post-development scenarios,
well, YMMV.<br>
<br>
Cheers,<br>
Bob<br>
<br>
<br>
</font><div><div class="h5">
<div>On 2/26/14 12:48 PM, Philippe Marschall
wrote:<br>
</div>
<blockquote type="cite">
<pre>On Tue, Feb 25, 2014 at 7:19 PM, Bob Arning <a href="mailto:arning315@comcast.net" target="_blank"><arning315@comcast.net></a> wrote:
</pre>
<blockquote type="cite">
<pre>I wonder if this doesn't point the way...
expire
self
greaseDeprecatedApi: 'WASession>>#expire'
details: 'This method might be reimplemented again. In the meantime,
if you just want to remove the Session from the Application, use
WASession>>unregister (#unregistered will be called as a notification
instead of #expired). Otherwise you should consider adding a Request Filter
to the Session that implements whatever behaviour you want in order to block
access to the Session.'.
^ self unregister
as well as...
WACache allInstances do: [ :e | e reap].
</pre>
</blockquote>
<pre>What problem exactly are you trying to solve? Do you have to do some
work when the session expires?
It is true that per default we only expire on every n-th session
creation. You can change this by swapping the reapingStrategy
WAAccessIntervalReapingStrategy. However keep in mind that:
- if somebody just creates sessions but never accesses them you may
still want to reap at some point
- reaping does not scale well, you have to walk over all the sessions
We are aware that the current situation is suboptimal and are working
on a replacement [1] but that may take a moment.
[1] <a href="http://lists.squeakfoundation.org/pipermail/seaside-dev/2014-February/005710.html" target="_blank">http://lists.squeakfoundation.org/pipermail/seaside-dev/2014-February/005710.html</a>
Cheers
Philippe
_______________________________________________
seaside mailing list
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br></div>