Provided by module: Tags: Session tag module
Creates a session bound scope. The session is
identified by a session key, given as an argument to the session tag.
The session key could be e.g. a value generated by
&roxen.unique-id; which is then transported by form
variables. An alternative which often is more convenient is to use the
variable client.session (provided by this module) together with the
<force-session-id> tag and the feature to set unique browser
id cookies in the http protocol module (located under the server ports
The key that identifies
the session. Could e.g. be a name, an IP adress, a cookie or the value
of the special variable client.session provided by this module (see
- life="number" (900)
Determines how many seconds the session is guaranteed to
persist on the server side. Values over 900 means that the session variables will be stored in a
disk based database when they have not been used within 900 seconds.
If used, the session variables will be immediatly written to the database.
Normally, e.g. when not defined, session variables are only moved to the database when they have
not been used for a while (given that they still have "time to live", as determined by the life
attribute). This will increase the integrity of the session, since the variables will survive a
server reboot, but it will also decrease performance somewhat.
- scope="name" (session)
The name of the scope that is created inside
the session tag.