RE: [PEAR-DEV] New Package Proposal: Enterprise A&A

Hi, ok the way I see it both A&A and LiveUser aim to provide the same goals and are somewhere in alpha and beta stage. For the most part the approach is the same (container/provider approach to allow different backends), but there are some structural differences. The backends that are supported atm are not the same however. I don't know if there is a language barrier or a communication barrier, because Tony seems to dispute this fact a lot. 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. So my question to Tony is: Is this a sensible course of action for you? Will you leave the code out in the open even if A&A is not chosen? 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 hope to find some time to look at the A&A source tonight and will then voice my vote. Regards, Lukas