Changes between Version 10 and Version 11 of MultipleAuthBackends

Timestamp:

Mar 14, 2006, 4:01:49 PM (19 years ago)

Author:

jkocherhans

Comment:

added clarification about sample code

MultipleAuthBackends

@@ -47 +47 @@
 }}}
 
-Note that the view is in charge of "logging in" a user, that is, the view must persist the id of the user somehow. A session variable is the easiest place, but a signed cookie would be desireable for those who don't want to use the session middleware. It would be nice if this were more convenient. It shouldn't be hard to do.
+Note that the view is in charge of "logging in" a user, that is, the view must persist the id of the user somehow. A session variable is the easiest place, but a signed cookie would be desireable for those who don't want to use the session middleware. It would be nice if this were more convenient. It shouldn't be hard to do. Also, in practice, all of this would probably happen in a decorator. Adding that much boilerplate code to every view would be a little ridiculous.
 
 For extra points, there should be ways of tying this all in with WSGI ;)