On Sat, 18 Dec 2004 02:23:00 +0100, Cees de Groot <cg@xxxxxxxxxxxx> wrote:
> Is session subclassing necessary? Frowned upon? A no-no? Because I don't
> just want to patch stuff up, I want to make this a
> superdupershiningexample of Seaside 2.5 use...
Well... I did make an attempt to factor things so that session
subclassing was less necessary than it had been previously - Session
was doing a few too many things, subclasses were proliferating, and,
short of Traits, reuse was getting difficult. The whole
#createRootFromRequest: thing could easily be done (and "should" be
done in 2.5) using a custom subclass of WAMain instead. But the one
thing session subclassing is still fairly necessary for, which Gardner
uses, is maintaining easily accessible per-session state like the
current wiki instance. One suggestion that's been made is to simply
have a properties dictionary on the base Session class so that rather
than needing a subclass with ivars, you just use "self session
propertyAt: #wiki" or some such. Thoughts on this?
> > The second problem is that the preferences system has been
> > considerably improved.
>
> Ah. That's a problem? ;-)
In this case :). But it shouldn't be much work to adapt to it.
Avi
|
