Re: New Package Proposal: Enterprise A&A
| From: | Markus Wolff | Date: | Wed, 15 Jan 2003 21:17:48 +0000 |
| Subject: | Re: New Package Proposal: Enterprise A&A | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-12510@lists.php.net to get a copy of this message | ||
On Wed, 15 Jan 2003 18:56:30 +0100
"Lukas Smith" <smith@backendmedia.com> wrote:
> When I said that I think it is wacked to have two single sign on classes
> in PEAR I say this because I think it would make sense to through as
> much weight as possible behind one single sign on system. Even though it
> is possible to make the to work with each other it is less than ideal
> and does not make the choice easier for the enterprise folks :-)
>
> To conclude:
> I would suggest deciding on one of them and merging whatever additional
> features or useful concepts the other has into it.
Agreement here, although personally I wouldn´t have a problem with
having two competing classes in PEAR as well (we have the same situation
with template classes and database abstraction anyway).
> For LiveUser: The code is already in the open. The question is if the
> current developers are willing to switch if A&A is chosen. I for one
> haven't started using LiveUser in production. If I understand Markuses
> situation correctly he is the original author of LiveUser but uses an
> older version in production that is incompatible with the PEAR version
> anyways. Arnaud seems to be the person closest to using PEAR::LiveUser
> in production.
I _used_ to use an older version in production ;-)
We´re currently developing a CRM and project management application
that´s going to hit the market in Q2 - LiveUser is definitely playing a
huge part there, so switching the package in this stage of development
(or even having all too heavy API breaks) certainly wouldn´t please me a
lot :-)
Regards,
Markus
--
Markus Wolff <wolff@21st.de>