Turbine depends completely on the container for session management. Here is a document describing Turbine's security service. This is the database implmentation. http://jakarta.apache.org/turbine/turbine-2/howto/security-howto.html
> -----Original Message----- > From: Lester Ward [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 03, 2003 11:09 AM > To: Turbine User Mailing List (E-mail) > Subject: Out of the box security > > > I see some great docs on how to override turbine's security > system to integrate with whatever you want; however, can > anyone point me to documentation of the .default. security > implementation in Turbine or just describe the basics? > Specifically, I'm interested in how it manages sessions and > uses cookies. I'm sure it is pretty straightforward, I just > can't find a description anywhere. > > The document on the Security Manager > (http://jakarta.apache.org/turbine/turbine-2/services/security -service.html) seemed a natural place for this, but it looks like no one has written it yet. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
