RE: Re[4]: [phplib] PHP4 and PHPLIB. Implementing authentication manually or using PHPLIB... From: Jeffrey A. Stuart (jstuart-php <email protected>)
Date: 01/03/01

I must say amen to this! I recently (like about 5 months) ago started to
use PHPLIB. And I for one will NEVER (well... probably never.. :)) switch
from using it with PHP... It lets me RAPIDLY prototype applications in PHP.
And personally, I do NOT see PHPLIB as being dead.. FAR from it! 

--
Jeff (FurBall)
WebOverdrive Newbie Tech Board
http://www.topniche.com/tech/
furball <email protected>

-----Original Message-----
From: Max A. Derkachev [mailto:kot <email protected>]
Sent: Wednesday, January 03, 2001 5:21 AM
To: Jeroen Laarhoven
Cc: PHPLIB
Subject: Re[4]: [phplib] PHP4 and PHPLIB. Implementing authentication
manually or using PHPLIB...

Hello Jeroen,

Wednesday, January 03, 2001, 12:08:09 PM, you wrote:

>>or adapt PHPLib to PHP4 sessions. (Hint: various implementations in
>>cvs tree, quite stable and robust)

JL> No, for a NEW project I would use PHP4 sessions.
JL> I see no reason to use the PHPLIB sessions, since PHP4 sessions is
almost a
JL> one2one copy of that functionality. (If you do not want to use the
User/Auth
JL> stuff.)

Yes, that's the reason to use a PHPLib session wrapper for PHP4
sessions - to use Auth. Some work should be done to make User work
with this approach (indeed, we need to rewrite User class, since in
stable PHPLib it extends Session class, but this won't work if you use
native PHP4 sessions).

Another reason is that you can use custom session storage using CT_*
classes (only file and mm storage modules are supported by PHP4 sessions
natively, no DB or other stuff, which is implemented in PHPLib),
and change session storage on the fly - a great feature of PHPLib.

And one more - I suppose in a serious project you'll implement some
functionality over raw PHP4 sessions. E.g. a custom function like
start_session() to automate session startup, which will set up session
storage module, necessary cache restrictions, various other options
and call session_start() at last. Instead of calling all those native
functions
every time by hand on every page. So is there something bad in using
PHPLib-like
Session class, that will do the same in a way you got used to?

JL> But: we should be *very* happy with these implementations for those who
have
JL> old projects that need to be ported to PHP4, using PHP4 sessions.

I guess PHPLib is the right thing. It makes a framework, where we
could embed a lot of functionality, that saves a lot of time and work.
People working hard now to make something like PHPLib - PEAR,
Binarycloud, etc. Why people think that there is no need in PHPLib
now, and it could only be useful when maintaining old projects? Who knows
...

--
Best regards,
Max A. Derkachev mailto:kot <email protected>
Symbol-Plus Publishing Ltd.
phone: +7 (812) 324-53-53
http://www.Books.Ru -- All Books of Russia

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>