Ive never subclassed it directly either. WASession is the only one ive used.<br><br><div class="gmail_quote">On Fri, May 27, 2011 at 9:00 AM, Ramon Leon <span dir="ltr"><<a href="mailto:ramon.leon@allresnet.com">ramon.leon@allresnet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 05/27/2011 01:13 AM, Julian Fitzell wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi list,<br>
<br>
I'm playing with some ideas at the moment and someone asked whether we<br>
shouldn't get rid of WARegistry in the process. Are many people using<br>
or subclassing WARegistry? If you are, could you share what you're<br>
doing with it?<br>
</blockquote>
<br></div>
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.<br>
<font color="#888888">
<br>
--<br>
Ramon Leon<br>
<a href="http://onsmalltalk.com" target="_blank">http://onsmalltalk.com</a></font><div><div></div><div class="h5"><br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">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>
</div></div></blockquote></div><br>