Session (gb.web)
This class is used for managing sessions.
Deze klasse is statisch.
Deze klasse reageert als
leesbaar /
schrijf statische reeks.
Statische eigenschappen
CookiePath
|
Return or set the path of the session cookie.
|
Id
|
Returns the session identifier.
|
Keys
|
Return the list of all keys associated with a value in the session as a string array.
|
Modified
|
Return or set if a session has been modified, and so should be saved to the disk.
|
Path
|
Return the session file path.
|
Prefix
|
Return or set the session identifier prefix.
|
Size
|
Return the session file size.
|
Timeout
|
Returns or sets the maximum duration of a session in seconds.
|
Type
|
Return or set the session type.
|
Unique
|
Return or set if the session must be unique.
|
Statische methode
Abandon
|
Drops the current session.
|
Exist
|
Return if a specific key is associated with a value in the session.
|
Load
|
Reloads the session from the disk.
|
Save
|
Saves the session to the disk.
|
What is a session?
A session allows you to keep the value of variables between two HTTP requests.
A session is a collection-like container identified by an arbitrary unique string
returned by the
Session.Id property.
That identifier has the following form:
<PREFIX>:<KEY>
-
<PREFIX>
is the prefix set to the Session.Prefix property, or the client IP address if no prefix is set.
-
<KEY>
is a 24 hexadecimal digits random number.
For example:
10.254.3.151:CFA76E086C00E18CF07A8EC
The session identifier is stored in a cookie named 'SESSION' in the client browser.
Storing values in session
The session can store values associated with string keys. You can store as many values as you want,
but there are restrictions: only native datatypes, arrays, and collections can be used.
The session contents are stored in the following file:
"/tmp/gambas." &/ System.User.Id &/ "session" &/ Session.Id
The session is automatically restored at program launch.
Session creation
A newly session is automatically created as soon as you store a session variable, and no session currently exists
(i.e.
Session.Id is
NULL).
If you call
Response.Begin too early, the session cannot be created, as the HTTP headers have already been sent. You have two solutions then:
Session destruction
You can abandon a session by using the
Abandon method.