Pure cookie-based session
Options recognized when using cookie-based sessions are slightly more restricted than general sessions.
Saves the data for this session to persistent storage
Delete the ‘expires’ attribute on this Session, if any.
Delete the cookie, and clear the session
Clear the contents and start a new session
Session object that uses container package for storage.
Saves the data for this session to persistent storage
If accessed_only is True, then only the original data loaded at the beginning of the request will be saved, with the updated last accessed time.
Revert the session to its original state from its first access in the request
Locks this session against other processes/threads. This is automatic when load/save is called.
*use with caution* and always with a corresponding ‘unlock’ inside a “finally:” block, as a stray lock typically cannot be unlocked without shutting down the whole application.
Unlocks this session against other processes/threads. This is automatic when load/save is called.
*use with caution* and always within a “finally:” block, as a stray lock typically cannot be unlocked without shutting down the whole application.
Deletes the session from the persistent storage, and sends an expired cookie out
Invalidates this session, creates a new session id, returns to the is_new state
Session proxy/lazy creator
This object proxies access to the actual session object, so that in the case that the session hasn’t been used before, it will be setup. This avoid creating and loading the session from persistent storage unless its actually used during the request.
Persist the session to the storage
If its set to autosave, then the entire session will be saved regardless of if save() has been called. Otherwise, just the accessed time will be updated if save() was not called, or the session will be saved if save() was called.
Loads a session given a session ID
Returns whether or not the session has been accessed
Extends python cookie to give digital signature support