Re: PHP 5 and Shared objects

What I meant is with PHP5 objects aren't treated as associated-variables so we don't have to serialize them, do we? so when I share an object over some session the object itself will actually stay alive and only the resource-id will be passed from file to file trhough same session, in other words the object is not being recreated while keeping its resource-id in a registered session variable, or I'm wrong? About the global object, it could be a security risk if the programmer is gonna use it badly (u r right) ----- Original Message ----- From: "Greg Beaver" <greg@chiaraquartet.net> To: "Salah Faya" <salah@e-touch.ws> Cc: <php-general@lists.php.net> Sent: Monday, April 21, 2003 11:05 PM Subject: Re: PHP 5 and Shared objects > This is already possible in php 4. However, both file1.php and > file2.php must begin with a session_start() call. > > A global object (common to all sessions) is a big security risk, I would > be surprised if it is considered a feature by the php team. You can > simulate such a thing yourself, by using a database, or a file on the > server backend that contains the serialized contents of the object, and > retrieve them in the beginning of each file. > > Regards, > Greg > -- > phpDocumentor > http://www.phpdoc.org > > Salah Faya wrote: > > As I've understood that PHP5 OOP will allow us to use a session-level shared > > objects smoothly, as in example: > > > > - file1.php > > session_register('myObj'); > > $myObj = new myClass(2003); > > $x = $myObj->year; // returns 2003 > > header('location: file2.php?PHPSESID='.session_id()); > > > > - file2.php > > if (isset($_SESSION['myObj'])) { > > $myObj=$_SESSION['myObj']; > > echo $myObj->year; // should also return 2003 > > } > > > > am I right? please correct me > > > > And if that's correct, is there a way to make a global object over all > > sessions (immortal object)? can this be a good feature to request? > > > > > > >