#1071: [patch] generic views (object_list/object_detail/date) should take
login_required as a parameter
-----------------------------+----------------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  jacob       
     Type:  task             |       Status:  new         
 Priority:  high             |    Milestone:  Version 0.92
Component:  Generic views    |      Version:  SVN         
 Severity:  major            |   Resolution:              
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by [EMAIL PROTECTED]):

  * priority:  normal => high

Comment:

 set priority to: high
 
 IMHO, it seems logical to get this patch in as soon as possible.
 i know that there are several projects in django regarding a move
 advanced authentication framework. But in neither GenericAuthorization
 or RowLevelPermissions i find references on how this will change
 Authentication
 of views.
 
 As long as views deal directly with there own authentication, i hope this
 patch
 can be adopted for completeness sake. So users can require login on all
 generic views
 django provides per default.
 
 When another system takes over, i guess all the login_required parameters
 will be stripped
 from generic views, so including a few more now to deal with
 authentication on
 list_detail and alike generic views doesn't seem like a problem to me.
 
 Ofcourse i'll leave the definition of 'problem' to the Django developers
 :)

-- 
Ticket URL: <http://code.djangoproject.com/ticket/1071>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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/django-updates
-~----------~----~----~----~------~----~------~--~---

Reply via email to