Re: PEAR and PHPLib compatibility?

Hi Jeff, > | much more features and is the future. PHPLib was yesterday... > | > Ahh well, the old 'manifest-destiny' argument lol. Use the because :) I have to admit that that were not my words, but rather a quote from a post on this thread a while ago, when I tried to figure out how to use LiveUser the first time. > "It's the future(tm)". Well, I'm not against using LiveUser, but I I am also not against anything new... > have two fundamental problems with it. 1) PHPLib isn't 'yesterday' - > it's 'well-tested', 'mature', and 'stable'. I don't > like the idea of Well, ok, stable... phplib is not maintaned anymore. There are no new releases anymore since a year or so and the latest official stable is not the one I actually use, because there are several drawbacks. > trusting my website security to a package that hasn't even reached > it's first 'release' version yet. 2)PHPLib is somewhat simpler, I Simpler. Sure. > think, than LiveUser, so I'm less likely to screw things up, lol. As :) > simple at this point - A) Allow users to login. B) Determine what user > a session is logged in as, so that I can retrieve user-specific data > from a database, C)Have users in either group 'admins' or group > 'users', and possibly a third group, and D) restrict access to certain > pages/resources to user of the admins group. A-D are also important for me and that's what phplib does just fine. Important for me is besides authentication the storage of session variables in the database. AND that's exactly the point I do not understand with LiveUser: Is there such a feature in LiveUser or not. I only read about rights and right storage containers, permissions etc. but nothing about the data storage feature. Hope that clears up in discussion. To make that clear: I still cannot imagine to migrate from my good-old phplib session management to LiveUser. Marko