On 10/27/05, David Stanek <[EMAIL PROTECTED]> wrote: > 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.
There's not much yet. Nothing formal. > In my ideal world this would be a very simple framework: > * Somehow tell TG that this page is protected (probably in the *.cfg > files) There are actually a few ways to configure that a page is protected: a decorator, a superclass and a filter (that may or may not currently use cfg variables... but that would be the place to do it). > * Somehow tell TG what module exports the identity interfaces (probably > in the *.cfg files) I don't know that this is defined yet. > * Define a generic interface or set of interfaces that are hooked where > authentication is needed This is the idea. > * Provide a sane out of the box implementation of the interfaces Yep. > 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). Exactly. What you've written is indeed the plan. It's not 100% there yet, and I have yet to really tinker with Jeff's work. But, what you've described is what will appear in 0.9. Kevin
