Re: [Phplib-users] php4 session fix, and some thoughts

[Giancarlo <gia...@na...>]

Is This is because $sess, in the phplib API, used to have its own 
$sess->in and $sess->pt, and used to treat these in a particular way, 
differently as userland properties, and used to make them persistent in 
its' own way (w/o a $sess->register), In practice, they were not 
userland session variables, but properties of the session object (as 
coming from source) that could be overriden in any instance, and stay 
persistent from that moment on...
The $sess->in property is a persistent switch that states wether that 
stuff has been autoloaded at init time, or not. So that it won't be 
reloaded on subsequent obj instantiation.

In the past we used to have something like

eval("\$sess->in=1") in the persistent code, that woud be evaluated on 
resumption. Now I dunno how to solve this, except using a non-$sess 
property for it, as register("sess_in")



> I like the idea of preserving sess->in instead.  page_close is already 

How can we preserve $sess->in if  $sess itself is not made persistent?
I don't think we should make $sess persistent, it never was. And that 
would mean to select just the properties we want to save, with a 
__sleep() function and defining persistent_slot("in"). Too much change, 
isn't' it?


> required again if you use register_globals off.
> 
> thanks for tracking this down.
> 
> Joe
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!
> Can't afford IT training? All 2003 ictp students receive scholarships.
> Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
> www.ictp.com/training/sourceforge.asp
> _______________________________________________
> Phplib-users mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phplib-users
>