> So, would anyone object if I threw out all the cruft in session.py
> relating to "application state"?  Is anyone apart from us using it?

I currently have three application state objects:

- User roles
- Preferences/customization
- "Where to go when you finish this general editing process"

The first two can be (and are) stored in other places - keeping them in the
session object just makes it easier to pull in everything quickly.  The
third really is part of a session, and needs to be associated with it
somehow.

So, I guess I need a way to keep a small amount of stuff in the session
object (or associated with it somehow).  It wouldn't be that hard to just
add it directly to my derived version of that object.  The ApplicationState
stuff does seem like a little bit more mechanism than I really need.

jon

Jonathan Corbet
Executive editor, LWN.net
corbet@lwn.net