On Fri, Jun 10, 2005 at 05:46:39PM -0600, Neil Schemenauer wrote: -> On Fri, Jun 10, 2005 at 04:28:17PM -0700, Titus Brown wrote: -> > in my rewrite/adaptation of the sessions code, I couldn't find a -> > use for anything other than the start_request, end_request, -> > abort_request, get_session, and expire_session functions. I don't -> > think anyone but the session manager class itself needs to poke -> > around in .sessions directly. -> -> I know of a number of applications that provide a web page that -> displays sessions and allows them to be manipulated (e.g. delete, -> join).
I would argue that the default SessionManager interface shouldn't cater to these needs. It's also unclear to me how the current transactional API in the session manager would deal with a session management Web page. When would abort_session or commit_session get called, for instance, on a session that was modified through a management interface? (I'm very confused about the session manager API distributed with Quixote, though, so you probably shouldn't listen to me.) --titus _______________________________________________ Quixote-users mailing list [email protected] http://mail.mems-exchange.org/mailman/listinfo/quixote-users
