Date: 07/21/01
- Next message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Bertrand Mansion: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
le 21/07/01 15:25, Björn Schotte ā bjoern <email protected> a écrit :
> * Bertrand Mansion wrote:
>> You should have a look at PEAR CVS tree. You will notice that PEAR now has
>> an Auth Class which is different from PHPLIB one.
>
> So what? :) PEAR doesn't say that there should exist
> only one implementation of one category (e.g. Authorization).
>
> PHPLIB's auth mechanism is very good, so I don't see
> why it shouldn't be integrated into PEAR.
I don't see neither why it should not be done. But it is not the point.
There already has been a discussion whether or not PHPLIB (just like Binary
Cloud) should be part of PEAR and the conclusion was no.
You can refer to :
http://marc.theaimsgroup.com/?l=pear-dev&m=99509236600858&w=2
http://marc.theaimsgroup.com/?l=pear-dev&m=99525653118799&w=2
http://marc.theaimsgroup.com/?l=pear-dev&m=99509428602729&w=2
But that does not make it worthless. PEARifying PHPLIB can only be good for
PHPLIB.
Regards,
Bertrand Mansion
Mamasam
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Bertrand Mansion: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

