Re: [Phplib-users] Current PHPLIB development questions

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

> 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.

In fact there used to be a few 'unsupported patches' around that used some 
workaround to get a 'login form' anywhere etc.
One of these used to set $auth->auth[uid]='form' so that it could call 
$auth->start anytime.
This is a typical example of something that would not work with the new auth, 
because the problem has been solved bothh by finding a bug and by eliminating 
 the 'unique entrance point' of the auth->auth[uid]=='form' state, that would 
block session everywhere and needed the cancel_login.

There are other 'usupported patches', that BTW never made their way into the 
official distrib, that would not work with the new auth. But all in all (ask 
those who looked at it), once you just read the new code and compare it with 
the old one, you understand that you don't want to go backwards anymore...

Gian