Re: [Phplib-users] Current PHPLIB development questions

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

I I'm 100% in agreement with Richard.
>
> It might make more sense to use the current "not stable" tree as a
> source for ideas, as Richard suggested, rather than try to actually
> merge everything or even most of what is in it into the stable version.
> I think that would be a very large and risky undertaking.

The dev snapshot has two new things: php4 session support & an auth redesign.

Php4 session support is quite stable and working by itself in the snapshot. 
It can be merged easily, it won't interfere with preexisting stuff. It really 
works. And is implemented much more simply than in the various previous 
'unsup' branches.
The new auth can be more tricky to distribute, and is based on some vital 
bugs found along  the way. These bugs have been backfixed into the cvs 
though. But as of now I do not necessarily see a problem in using it as a 
dropin replacement: it will work mostly everywhere, especially if the app 
sticked to the API, and didn't use to call directly functions as 
$auth->start() or $sess->freeze() or similar functions that were supposed not 
to be used but to be called by phplib. The cancel_login is the only thing not 
supported, it simply has no effect.

Gian