Re: PEAR and PHPLib compatibility?

From: Date: Fri, 12 Mar 2004 12:07:37 +0000
Subject: Re: PEAR and PHPLib compatibility?
References: 1 2 3 4 5  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-11253@lists.php.net to get a copy of this message
Hi Lukas, > No, storing of non authentication and permission related things is not > on the feature list. There is a patch pending for commit which will > allow attaching other data to the user, like email etc from the admin API. ok, now I eventually got it. So that is a substantial difference in functionality between LiveUser and phplib's session managment! That answers my questions and I now understand that I did not simply miss the point in the description: it simply doesn't exist at all... :) ok > Anyways: should these "session variables" be stored permanemently or > only for the session lifetime? Of course the session vars should be stored permanently in the storage container. I advise you to have a look at the phplib docus. Kristian Koehntopp et al did a great job in implementing session management before php itself could handle it. And still it seems then to be the only library which offers classes for handling session data (using php4 own session handling also) for users or user groups with own sets of permissions and various ways of authentication. But I guess as you say LiveUser could be used together with an add-on or extension to get the wanted functionality. Implementing that inside LiveUser itself seems to be against the project goals: you write that you cache the permission data and so on for speed reasons... well, the session handling I am talking about would have to access the storage container TWO times per page creation: once to read the actual variable set and the second time to write the changes back. That's not what you intend, I guess. So, we have to stick with phplib still for some time... Perhaps somebody could be found who might port phplib's session management to PEAR?! Greetings, Marko

« previous php.pear.general (#11253) next »