On 13 March 2003, Andrew Kuchling said:
>    * Factor out the session management interface from
>      SessionPublisher.  SessionPublisher will become a near-trivial
>      subclass of Publisher; Publisher will default to using
>      a null session manager while SessionPublisher will default
>      to the current in-memory session storage.

It would be nice to get rid of SessionPublisher entirely -- ie. the
Right Way to setup a session-managing Quixote app is to create a
Publisher with a real SessionManager object.

Or do you just want to hang on to SessionPublisher for backwards
compatibility?

        Greg
--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org