On Wed, 18 Sep 2002 23:08, you wrote: > I definitly agree that having a working extend user is crucial for 2.2. > The other one I would toss out (although the scope might be too much) is to > integrate the new Security schemes that have been tossed out. > > I think doing those two things would give people a reason to upgrade to > 2.2, versus staying with 2.1. Right now, while the decoupled stuff is > cool, it adds more complexity as well. And doesn't seem to be a compelling > reason to upgrade. Fixing the extend user abilty and pluggable security do > seem compelling.
Hi Eric, I can understand the desire for pluggable security, but the current SecurityService is fine for most web applications. The beauty of Turbine is that you don't have to use the Turbine SecurityService if you don't like it (ie: if your app doesn't have a requirement for users, roles, groups and permissions just don't use the SecurityService and implement your own). I think that if we delay the release of Turbine 2.2 until pluggable security is implemented, we could be waiting for a long time, so I would vote to leave pluggable security for Turbine 2.3. What do others think? -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
