> The application creators weren't thinking about interoperability of their
> applications because there are no such guidelines for making interoperable
> applications. Interfaces and componentization would give Django the
> opportunity to define some standard interfaces like IUser and give Django
> > However, that's a good reason to have sessions pluggable -- if
> > persistence is important, then you need db sessions.
What about file for sessions like in php? I want sessions to be very
fast, but
memory solution is bad for development and production because you lose
all your session data b
Blog post here: http://www.buriy.com/2007/may/12/django-openid-users/
Download here: http://www.buriy.com/media/openid-solution.zip
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
On May 11, 5:30 am, Simon Willison <[EMAIL PROTECTED]> wrote:
> I'm working on a new component for my Django OpenID package which will
> provide support for associating one or more OpenIDs with a
> django.contrib.auth User. As part of this, I want to include the
> ability to register for a new use
