CACMS - Golden Content Management System
Session Attributes

Session attributes are at the core of CaCMS. They are used in many places to keep some state. You can see them from time to time in the address line of your browser.

cacms.mode The working mode of CaCMS. Possible values: show, edit or admin
cacms.action Action to execute. Each component may register its own actions.
cacms.userid ID of current user. -1 for visitors. This session attribute is protectec and cannot be updated by means of GET or POST.
cacms.containerid ID of current container. -1 for a new container or -2 if no container exists.
cacms.reqid.xhtml Request ID of current index.html. Important for components who may appear more than once per container, because they should have a reliable way to identify request boundaries.
cacms.reqid.css Request ID of current index.css. Important for components who may appear more than once per container, because they should have a reliable way to identify request boundaries.
(M)Any others Components may use their own session attributes whenever they want. The session therefore may contain many more session attributes then the ones listed above.

Before version 0.10.2 all parameters of a GET or POST request (besides the protected ones) were added to the session as one of the first things of handling the request.

To think about

Since version 0.x.y there exists a more sofisticated way to treat session attributes. This allows to modify the session after the request was handled, but before the answer is returned. The behavior is specified in a suffix of the request parameter like this:

SuffixMeaning
.b-Parameter should be removed before handling the request.
.b+ (or no suffix)Parameter should be added/updated before handling the request this is the default behaviour if no suffix is given.
.a-Parameter should be removed after handling the request.
.a+Parameter should be added/updated after handling the request.

('b' for before, 'a' for after)