very true, mcvdmvs.
session vars have an identical scope to setcookie() vars. They are user specific.
It is impracticle for session and cookie vars to be available to all users because we can do this just by setting the variable within a global include script or something.
Example (obvious, but good for newbies):
Let's say that a user has registered on our site and in that registration, the told us that they wanted to see the date on their start page to be in m-d-Y format. By default, we have set the date format to be Y-m-d.
As a result of the users registration and subsequent login, a session variable was set called 'my_date' using:
$my_date = date("m-d-Y"

;
session_register("my_date"

;
filename: global.inc.php
<?php
/*
initiate the session so we can
access any registered session variables.
*/
session_start();
/*
an application-level variable
(one that is accessible to everyone
since we are setting it within the script
as a generalized variable (no special
parameters, access, etc.). Basically, it
is global in the scope of this script and all
scripts that include this one.
*/
$date = date("Y-m-d"

;
/*
if session registered variable 'my_date'
exists, reassign $date to $my_date
*/
if($my_date) {
$date = $my_date;
}
?>
Now, whenever we have a script that we want to access $date, we can use
(for PHP >= PHP 4.0.1pl2):
include_once($DOCUMENT_ROOT."/globals/php/global.inc.php"

;
(for others):
include($DOCUMENT_ROOT."/globals/php/global.inc.php"

;
A session now has already been initiated, we have determined that the user-level variable $my_date is set, and we have reassigned $date with $my_date.
So, in conclusion, session variable and cookie variable data are strictly user-level accessible because to do otherwise would be redundant and pointless; we can just set a variable within our code somewhere and access it globally (if done right).
Hopefully, I have made sense here and someone has gotten something out of this. ;-)
Chad. ICQ: 54380631