[Seaside] WARegistry

Jon Paynter kittle31 at gmail.com
Fri May 27 17:18:29 UTC 2011

Ive never subclassed it directly either.  WASession is the only one ive

On Fri, May 27, 2011 at 9:00 AM, Ramon Leon <ramon.leon at allresnet.com>wrote:

> On 05/27/2011 01:13 AM, Julian Fitzell wrote:
>> Hi list,
>> I'm playing with some ideas at the moment and someone asked whether we
>> shouldn't get rid of WARegistry in the process. Are many people using
>> or subclassing WARegistry? If you are, could you share what you're
>> doing with it?
> Never subclassed it directly, but subclass WAApplication plenty which is
> itself a WARegistry subclass.  Usually I just want to get access to the
> request at the main application entry point before a particular session is
> invoked, a good example would be for rate limiting request using memcached
> or handling a response not meant for a session like a server heartbeat check
> from a load balancer or something.  Maybe responding with a generated
> sitemap as well bypassing all the session machinery.
> --
> Ramon Leon
> http://onsmalltalk.com
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110527/57da9750/attachment.htm

More information about the seaside mailing list