Index: branches/5.0.x/core/kernel/session/session.php
===================================================================
diff -u -r12202 -r12299
--- branches/5.0.x/core/kernel/session/session.php	(.../session.php)	(revision 12202)
+++ branches/5.0.x/core/kernel/session/session.php	(.../session.php)	(revision 12299)
@@ -1,6 +1,6 @@
 <?php
 /**
-* @version	$Id: session.php 12202 2009-08-05 16:52:45Z dmitrya $
+* @version	$Id: session.php 12299 2009-08-17 01:51:27Z dmitrya $
 * @package	In-Portal
 * @copyright	Copyright (C) 1997 - 2009 Intechnic. All rights reserved.
 * @license      GNU/GPL
@@ -12,45 +12,49 @@
 * See http://www.in-portal.net/license/ for copyright notices and details.
 */
 
-/*
+defined('FULL_PATH') or die('restricted access!');
 
+/*
 The session works the following way:
 
 1. When a visitor loads a page from the site the script checks if cookies_on varibale has been passed to it as a cookie.
 2. If it has been passed, the script tries to get Session ID (SID) from the request:
 3. Depending on session mode the script is getting SID differently.
-   The following modes are available:
 
-		smAUTO -						Automatic mode: if cookies are on at the client side, the script relays only on cookies and
-												ignore all other methods of passing SID.
-					   						If cookies are off at the client side, the script relays on SID passed through query string
-					   						and referal passed by the client. THIS METHOD IS NOT 100% SECURE, as long as attacker may
-					   						get SID and substitude referal to gain access to user' session. One of the faults of this method
-					   						is that the session is only created when the visitor clicks the first link on the site, so
-					   						there is NO session at the first load of the page. (Actually there is a session, but it gets lost
-					   						after the first click because we do not use SID in query string while we are not sure if we need it)
+The following modes are available:
+- AUTO
+Automatic mode: if cookies are on at the client side, the script relays only on cookies and
+ignore all other methods of passing SID. If cookies are off at the client side, the script relays on SID
+passed through query string and referal passed by the client. THIS METHOD IS NOT 100% SECURE, as long as
+attacker may get SID and substitude referal to gain access to user' session. One of the faults of this method
+is that the session is only created when the visitor clicks the first link on the site, so there
+is NO session at the first load of the page. (Actually there is a session, but it gets lost after
+the first click because we do not use SID in query string while we are not sure if we need it)
 
-  	smCOOKIES_ONLY -		Cookies only: in this mode the script relays solely on cookies passed from the browser
-  											and ignores all other methods. In this mode there is no way to use sessions for clients
-  											without cookies support or cookies support disabled. The cookies are stored with the
-  											full domain name and path to base-directory of script installation.
+- smCOOKIES_ONLY
+Cookies only: in this mode the script relays solely on cookies passed from the browser and ignores
+all other methods. In this mode there is no way to use sessions for clients without cookies support
+or cookies support disabled. The cookies are stored with the full domain name and path to base-directory
+of script installation.
 
-  	smGET_ONLY -				GET only: the script will not set any cookies and will use only SID passed in
-  											query string using GET, it will also check referal. The script will set SID at the
-  											first load of the page
+- smGET_ONLY
+GET only: the script will not set any cookies and will use only SID passed in query string using GET,
+it will also check referal. The script will set SID at the first load of the page
 
-  	smCOOKIES_AND_GET -	Combined mode: the script will use both cookies and GET right from the start. If client has
-  											cookies enabled, the script will check SID stored in cookie and passed in query string, and will
-  											use this SID only if both cookie and query string matches. However if cookies are disabled on the
-  											client side, the script will work the same way as in GET_ONLY mode.
+- smCOOKIES_AND_GET
+Combined mode: the script will use both cookies and GET right from the start. If client has cookies enabled,
+the script will check SID stored in cookie and passed in query string, and will use this SID only if both
+cookie and query string matches. However if cookies are disabled on the client side, the script will work
+the same way as in GET_ONLY mode.
 
 4. After the script has the SID it tries to load it from the Storage (default is database)
-5. If such SID is found in the database, the script checks its expiration time. If session is not expired, it updates
-	 its expiration, and resend the cookie (if applicable to session mode)
-6. Then the script loads all the data (session variables) pertaining to the SID.
 
+5. If such SID is found in the database, the script checks its expiration time. If session is not expired,
+it updates its expiration, and resend the cookie (if applicable to session mode)
 
+6. Then the script loads all the data (session variables) pertaining to the SID.
 
+
 Usage:
 
 $session = new Session(smAUTO); //smAUTO is default, you could just leave the brackets empty, or provide another mode
@@ -60,7 +64,6 @@
 $session->SetCookieName('my_sid_cookie');
 $session->SetGETName('sid');
 $session->InitSession();
-
 ...
 
 //link output:
@@ -69,7 +72,11 @@
 
 */
 
-//Implements session storage in the database
+
+/**
+ * Implements Session Store in the Database
+ *
+ */
 class SessionStorage extends kDBBase {
 
 	var $Expiration;
@@ -397,6 +404,7 @@
 define('smGET_ONLY', 3);
 define('smCOOKIES_AND_GET', 4);
 
+
 class Session extends kBase {
 	var $Checkers;
 
@@ -1162,6 +1170,4 @@
 		return $ret;
 	}
 
-}
-
-?>
\ No newline at end of file
+}
\ No newline at end of file