<session></session>

Provided by module: Session tag module

Creates a session bound scope. The session is identified by a session key, given as argument to the session tag. The session key could be e.g. a key generated by &unique-id;, transported by form variables.

Attributes

id="string": The key that identifies the session. Could e.g. be a name, an IP adress or a cookie.
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.
force-db: 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.

		<session></session> Provided by module: Session tag module Creates a session bound scope. The session is identified by a session key, given as argument to the session tag. The session key could be e.g. a key generated by &unique-id;, transported by form variables. Attributes id="string" The key that identifies the session. Could e.g. be a name, an IP adress or a cookie. 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. force-db 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.