On 1/12/06, Rubic <[EMAIL PROTECTED]> wrote: > > Jeff Watkins wrote: > > Currently the Identity framework relies upon > > providers which will be closely coupled to the > > underlying DB library (or IMAP or LDAP or whatever). > > By "currently", do you mean indefinitely? > > > That's just life. > > No, that's a design decision. > > I came to TurboGears with the perception that > SQLObject was optional, but if TG components > are going to be tightly coupled to it then I > may need to reevaluate my choices.
I'm not sure I understand the particular complaint here. Jeff said that the identity providers are coupled to whatever datastore is holding the identity information. Which, to me, makes sense... that's the whole job of the provider: look up the information in an appropriate place and make it available for authentication/authorization. TurboGears comes with core components, and the high-level features make use of those components. But, some components (such as templates and identity) allow you to switch out core pieces as your application demands. Other features are more tied to the core components (DataController/sqlwidgets), but you can still get lots of value out of TurboGears by using other parts. So, you can use TurboGears without SQLObject. If something prevents that, it's a bug. But, you won't necessarily be able to use *all* of the features. Or, in the case of identity, the built-in provider is for SQLObject, but you can still create/use a different identity provider that talks to some other database. Does that clear it up? Kevin
