From 58626b35b0b272c5e37a7a22c3efb68145dab14a Mon Sep 17 00:00:00 2001 From: Derek Allard Date: Mon, 11 Feb 2008 01:38:10 +0000 Subject: removed mention of last_visit from session docs --- user_guide/libraries/sessions.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'user_guide/libraries/sessions.html') diff --git a/user_guide/libraries/sessions.html b/user_guide/libraries/sessions.html index 03d15f183..117801109 100644 --- a/user_guide/libraries/sessions.html +++ b/user_guide/libraries/sessions.html @@ -103,7 +103,7 @@ even add your own data to a user's session, but the process of reading, writing,
  • The user's unique Session ID (this is a statistically random string with very strong entropy, hashed with MD5 for portability, and regenerated (by default) every five minutes)
  • The user's IP Address
  • The user's User Agent data (the first 50 characters of the browser data string)
    • -
  • The "last activity" and "last visit" time stamps.
    • +
  • The "last activity" time stamp.

    • The above data is stored in a cookie as a serialized array with this prototype:

    @@ -113,8 +113,7 @@ even add your own data to a user's session, but the process of reading, writing,      'session_id'    => random hash,
         'ip_address'    => 'string - user IP address',
         'user_agent'    => 'string - user agent data',
    -     'last_activity' => timestamp,
    -     'last_visit'    => timestamp
    +     'last_activity' => timestamp
    )

    If you have the encryption option enabled, the serialized array will be encrypted before being stored in the cookie, -- cgit v1.2.3-24-g4f1b