I was wondering how the TG developers (Jeff especially) would consider
the relative stability of the Identity module at this point?
As of right now, I've been writing my applications without regard to
authentication because I'm going to need to write a moderately complex
authentication back end for interfacing with Active Directory/LDAP and
KEYS (some customish authentication framework that's in use here at
Kansas State).
My question is kind of simple: should I start on this portion of the
project? Is the identity framework going to remain stable in (at
least) the medium term such that custom SOProviders and such are going
to keep working? Is the code for Identity at a happy place that heavy
customization makes sense?
actually what you need to do is create a LDAPProvider module, sin ce SO stands for SQLObject, I have been thinking of refactoring that a bit but as Michele says below no api changes so I'm not sure if that will be possible in the near future.
Thank you for your time,
Travis Bradshaw
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
