Phillip J. Eby wrote: >> Session: >> An instance of this represents one user/browser's session. >> SessionStore: >> An instance of this represents the persistence mechanism. This >> is a functional component, not embodying any policy. >> SessionManager: >> This is a container for sessions, and uses a SessionStore. This >> contains all the policy for loading, saving, locking, expiring >> sessions. > > > Which of these is responsible for managing client-side state? (i.e. > cookie reading, setting, expiration, and refresh?)
SessionManager is responsible for expiration. I'm not sure what you are thinking of for refresh. Updating last-accessed time? That would be the SessionManager as well. Cookies are not handled at all by these objects -- that's one of those boring details I think is best left to library users (frameworks, services, middleware), or put in another object. -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
