> 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.
So I can write my own identity provider that doesn't depend on SQLObject. From Cliff Wells' earlier post it appeared that he had to use SQLObject in order to use Identity. > Does that clear it up? Yes. Thanks.
