Sessions in MoinMoin are implemented using a special session service that can be configured in cfg.session_service. Code using the session framework currently includes: the superuser "change user" functionality, see HelpOnSuperUser the visited pages trail

cookie_name None Part of the session cookie name. None means to create the name from some url parts, 'siteidmagic' means use cfg.siteid (name of config file), anything else will be just used as is. cookie_domain None Domain used in the session cookie. cookie_lifetime (0, 12) Cookie lifetime in hours, can be fractional. First tuple element is for anonymous sessions, second tuple element is for logged-in sessions. For anonymous sessions, t=0 means that they are disabled, t>0 means that many hours. For logged-in sessions, t>0 means that many hours, or forever if user checked 'remember_me', t<0 means -t hours and ignore user 'remember_me' setting - you usually don't want to use t=0, it disables logged-in sessions.

Likely the only interesting item is cookie_lifetime.

The default cookie_name = None creates a different cookie name and separate sessions for each wiki. If you want separate sessions for your wikis, you can't use cookie_name = 'siteidmagic' because that always would set the name to MOIN_SESSION_wikiconfig. So either explicitly set a unique cookie_name for each wiki or use cookie_name = None.

E.g. wiki1.example.org and wiki2.example.org. If you like shared sessions, shared user profiles, use this in your farmconfig:

E.g. example.org/wiki1 and example.org/wiki2. If you like shared sessions, shared user profiles, use this in your farmconfig:

E.g. example.org:8000 and example.org:8001. If you like shared sessions, shared user profiles, use this in your farmconfig:

As an extension programmer, in order to use session variables, you can use request.session like a dict, values stored there are automatically saved and restored if a session is available. Here's an example macro using the session code: