Re: PHP 4.0 Bug #5152: Object passed in a session generateserrors when member functions are called

SS>> Nope, I think you are missing the point of this discussion. SS>> SS>> In a given web site, you may have two or more areas which SS>> coexist in one framework, but which are nevertheless SS>> developed separately (so they do not share code which SS>> accesses session objects). Users of this site can switch Then they should use different sessions. If they don't share objects, why should they share sessions? I still think disciplining users a bit on this is a Good Thing :). But some users tend to disagree. That's why I proposed "hidden object" approach - it won't mislead you into thinking you can use object without defining its class, and it would preserve object's class through the session. -- Stanislav Malyshev stas@zend.com +972-3-6139665