Is there any documentation describing how the identity framework works?
Or maybe a plan for the vision? I have only been able to piece together
bits while trying to keep up with this list.
In my ideal world this would be a very simple framework:
* Somehow tell TG that this page is protected (probably in the *.cfg files)
* Somehow tell TG what module exports the identity interfaces (probably in the *.cfg files)
* Define a generic interface or set of interfaces that are hooked where authentication is needed
* Provide a sane out of the box implementation of the interfaces
This way very custom applications can just implement the interfaces and
through the magic of duck typing everything just works. For instance,
the traditional User object can be the sane out of the box
implementation. But say you don't use a database for
authentication...that is easy as a new implementation of the
interface(s).
--
David Stanek
www.roninds.net
- [TurboGears] Re: Problems with Inheritence David Stanek
- [TurboGears] Re: Problems with Inheritence Kevin Dangoor
- [TurboGears] Re: Problems with Inheritence Jeff Watkins
- [TurboGears] Re: Problems with Inheritence Jeff Watkins

