<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
I guess I just use WAApplication for everything... seeing as I how I don't understand any of the underlying architecture, I'm with whatever as long as I can still make an entry point ;)<div><br></div><div>RS<br><br>> From: jfitzell@gmail.com<br>> Date: Fri, 27 May 2011 14:10:22 +0100<br>> Subject: Re: [Seaside] WARegistry<br>> To: seaside@lists.squeakfoundation.org<br>> <br>> On Fri, May 27, 2011 at 10:08 AM, Philippe Marschall<br>> <philippe.marschall@gmail.com> wrote:<br>> > 2011/5/27 Julian Fitzell <jfitzell@gmail.com>:<br>> >> 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.<br>> >> …<br>> ><br>> > I would support that in favor of a dedicated session store and a<br>> > dedicated document store. The current solution with document handlers<br>> > and sessions stored is quite messy for example because sessions can be<br>> > looked by cookie but documents can't.<br>> <br>> Yep, definitely part of what I'm playing with (though slightly<br>> tangential). It wouldn't be hard to accommodate WARegistry as a<br>> concept (a Dispatcher with dynamic keys, maybe or maybe not expiring -<br>> but probably without cookie support) but I think WAApplication will<br>> end up not being a subclass if this idea works out.<br>> <br>> I'm still interested in hearing from the list more generally - if<br>> you're using WARegistry for anything, please speak up.<br>> <br>> Julian<br>> _______________________________________________<br>> seaside mailing list<br>> seaside@lists.squeakfoundation.org<br>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br></div> </body>
</html>