Code

Changes between Version 10 and Version 11 of MultipleAuthBackends


Ignore:
Timestamp:
03/14/06 14:01:49 (8 years ago)
Author:
jkocherhans
Comment:

added clarification about sample code

Legend:

Unmodified
Added
Removed
Modified
  • MultipleAuthBackends

    v10 v11  
    4747}}} 
    4848 
    49 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. 
     49Note 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. 
    5050 
    5151For extra points, there should be ways of tying this all in with WSGI ;)