[Seaside-dev] expiry policies

[Randal L. Schwartz]

>>>>> "Julian" == Julian Fitzell <jfitzell at gmail.com> writes:

Julian> Another attempt at improving expiry, this time through an external
Julian> WACache. The cache is pluggable for expiry policy, aciton to take on
Julian> expiry, strategy to use incase of cache miss (might allow pulling
Julian> sessions in from disk), and cache reaping strategy (when to run a
Julian> reap).

I haven't seen the code, but as a use case, I'd like
to be able to say:

   self session expireInNoLessThanSeconds: (86400 * 7).

to make a particular session have a long expiry, if it contains a callback URL
to validate a user or something.  I don't think there's an easy way
to decide expiry on a per-session basis.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion