Re: OSUser status and improvements

Hi Scott.

Last year I developed what I was calling OSUser 2 but unfortunately, the 
OSUser community rejected it.  The main reason was that any providers 
would have to be re-written because my interfaces were different.  The 
client side use was almost the same though.  I didn't consider that 
deficiency to be a deal killer because OSUser isn't even 1.0, and I felt 
the current incarnation of OSUser is too broken underneath to work 
with.  My opinion was the minority.  If you want to enhance OSUser as I 
have done, you will come up against resistance too.  I have since given up.

Good luck to you.

~ Dave Smiley

>Guys,
>
>I went ahead to try and create a delegating user provider for OSUser (so
>that LDAP could be used properly), but I found the codebase a tangled
>mess - it was very difficult for me to add changes, and nearly impossible
>to test.
>
>I'm keen to make a whole lot of improvements to OSUser, and I'm wondering
>if there is anything that I should be aware of, or anyone else who wants
>to help.
>
>Things to do:
>- create interfaces for everything
>- programmatic configuration (rather than only XML based)
>- simplify everything
>- create unit tests
>
>Whilst there is probably a lot of complexity there that is needed, I feel
>that a lot can be got rid of.  Is there anyone who can help steer me in
>the right direction?
>
>Cheers,
>Scott
>


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click