Re: Proposed Package (again): Enterprise Authentication & Authorization
| From: | Markus Wolff | Date: | Thu, 06 Feb 2003 21:31:49 +0000 |
| Subject: | Re: Proposed Package (again): Enterprise Authentication & Authorization | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13022@lists.php.net to get a copy of this message | ||
On Thu, 6 Feb 2003 11:32:08 -0600 (CST)
Tony Bibbs <tony@tonybibbs.com> wrote:
> Man, has this come full circle.
Ain´t democracy great? ;-)
> Well, while the folks working on LiveUser had the best intentions on
> working with me on this, time committments have prevented them from giving
> this the attention it needs and have since encouraged me to repost this
> here. The idea is after things slow down we will revisit merging again
> and while I welcome this I don't plan on holding my breath.
>
> To prevent re-posting everything, here is the original proposal I
> submitted:
>
>
> http://marc.theaimsgroup.com/?l=pear-dev&m=104256945332548&w=2
>
> Questions and comments are welcome again but I hope we have beat this to
> death and a vote can take place soon...
Well, so here´s my +1 for you in case I didn´t give that in the previous
thread. A quick summary to all who have not followed the thread and
don´t have the time to catch up:
- Enterprise A&A and LiveUser both try to achieve the same goals
- The packages have different API´s. Therefore it might make sense to
have both packages in PEAR, so the user has a broader choice - not
every developer likes the same API styles.
- As far as I´ve seen, Enterprise A&A follows PEAR coding guidelines and
the code seems well-documented.
- While LiveUser started out using just an RDBMS to store its data, EA&A
is using RPC calls from the beginning (SOAP I guess - this feature is
planned for LiveUser as well, but not yet implemented).
Unfortunately, I didn´t have enough time to dig into the differences
between the packages any further (which is why we postponed the
discussion of a possible merge), so this is all I can say ATM.
Regards,
Markus
--
Markus Wolff <wolff@21st.de>