> > I like it. How do you specify the controllers you want to use? I'm > > thinking from the point of view of a Turbine security service, you > > would probably want to configure that from the properties file. > > > > In fact, I think it works pretty much like the thing I came up with. > > Good work! ;-) > > If people are interested (please give me your thoughts) I will port the > db service to this as well as finish off an XML implementation that I > started as well as create a Turbine binding. If people are seriously > considering this I will clean everything up and present as a package in > a week or two.
If you can package it so that: * it compiles with HEAD, * it is pluggable and configurable via TR.props, * it provides the following implementations: DB-based (traditional Turbine style), XML-based and null (that is, no security, everything is allowed), then I would heartily stand by it as a Next Generation security service. Even more, I would push for having the null implementation as Turbine's default. > - Dan Best regards, -- Gonzalo A. Diethelm [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
