Jon,

I have been spending a considerable amount of time attempting to understand
how Turbine works, both by looking through CVS as well as stepping through
code. I apologize for my ignorant questions, but spending three weeks with
the product compared to the amount of time you've spent writing the system
leaves me at a disadvantage. I assure you, I am not intentionally asking
stupid questions nor am I just posting a question because I'm too lazy to
look through CVS. Turbine is a very complex system and there are many areas
I have not even touched. When we get stuck, the mail list is about the only
place we can turn to for guidance.

BTW, looking in CVS at the latest version of
org.apache.turbine.om.security.peer.UserPeer, it is implemented as an
interface. It no longer contains any code, it just extends
org.apache.turbine.services.security.impl.db.entity.UserPeer, which is in
the attic in CVS. Please educate.

Thanks!

Regards,
Jay Turpin
Intel Corporation

-----Original Message-----
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 11:03 PM
To: turbine-dev
Subject: Re: Plans for TurbineGroup, TurbineRole, etc.


on 5/8/01 9:44 PM, "Turpin, Jay" <[EMAIL PROTECTED]> wrote:

> The version we are using is from the end of March, so we could get a
> buildable version of Turbine that worked with Jetspeed without too much
> modification.

If only the archives had been available. I posted here several times
notifying people that Group is now an interface.

> Just noticed that Group is now an interface, but GroupPeer still isn't.

Peer's don't need to have interfaces. There is no UserPeer interface.

> Do
> you plan to morph all of the security objects into interfaces to support
> LDAP and DB?

The stuff in CVS can be adapted to support LDAP by providing a more complete
LDAPSecurityService.

Please spend some time looking at the code in CVS before asking more
questions because all of the answers are there. It doesn't that take much
effort.

thanks,

-jon


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to