Re: New Package Proposal: Enterprise A&A

Man, that opened a can of worms for me. Here are more thoughts: On Wed, 15 Jan 2003, Arnaud Limbourg wrote: > If everybody agrees on keeping one package it does not really matter, > it is more an API question for people already using it. Good question. My thoughts here are maybe the answer is we branch LiveUser so you can continue using it to scratch your itch. Then we can work on an approach together and then worry about API issues when it is time to merge back into the LiveUser project. Or maybe live user goes away after we complete our merge and get things stable...if supporting as much of the original live user API is a requiremene we come up with I"m fine with that...it would minimize the impact users of LiveUser when they go to upgrade. > We could then start from ground-up, build a common API and take the > best of the two packages. Wrapper could be provided as well to make > things easy. My needs for an A&A system aren't immediate. As long as I know what the service API is and what the user object will look like, we (Geeklog Developers) can stub out dummy functions that let us continue with other tasks. Personally I wouldn't mind moving all my XML-RPC stuff over to SOAP (SOAP is a core competency I have now) and taking the best of both worlds. A ground-up effort could still 'borrow' code from both packages making getting an alpha release up in short order possible. If there will be one or two other heads to throw at this, that sounds quite agreeable to me. --Tony