#5382: create_update.delete_object always needs a confirmation page
-----------------------------------+----------------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  nobody       
     Status:  closed               |            Component:  Generic views
    Version:  SVN                  |           Resolution:  wontfix      
   Keywords:  delete_object        |                Stage:  Unreviewed   
  Has_patch:  0                    |           Needs_docs:  0            
Needs_tests:  0                    |   Needs_better_patch:  0            
-----------------------------------+----------------------------------------
Comment (by Przemyslaw Wegrzyn <[EMAIL PROTECTED]>):

 What is the reason for this statement? I mean - has it technical or
 philosophycal background?
 
 I see nothing wrong in GET requets changing the server-side state,
 actually it is not uncommon (e.g. webmail app marking the mail as read,
 upon displaying the mail, to mention the most trivial case).
 
 Assuming that I do need POST requests to delete objects, I have to add
 some artifical JavaScript code to submit a POST request (as stated before,
 I use plain links for deletion).

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5382#comment:2>
Django Code <http://code.djangoproject.com/>
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to