On 10/25/05, Jeff Watkins <[EMAIL PROTECTED]> wrote: > I still have to address folks like yourself who have alternate model > requirements -- there should be a way to tell the TurboGears identity > module what model classes to use.
It seems like this will only go so far... some people may have a model that looks different (different class names and attribute names), but that has the same basic features. For those, you could add configuration to determine what model to use. But, others may need to configure an entirely different provider. I'd say that the ability to configure an entirely different provider is more important than the ability to configure a different model (because it's a superset of functionality). Kevin
