I did not read the sources of the admin module devoted to deleting an
item, but I think the problem is not in the admin interface but in
html forms.
Html forms allow only GET and POST, but no DELETE and PUT. Given the
REST common-sense rule "whenever you POST, ask the user" the admin
interface - a
Thanks Euan - I think that clarifies things. Thanks very much for your
responses!
Margie
On Jul 7, 8:50 am, "euan.godd...@googlemail.com"
wrote:
> I think in the strict REST sense, it would be best to POST to one URL
> with the list of object IDs to delete to set this action up and then
> redire
I think in the strict REST sense, it would be best to POST to one URL
with the list of object IDs to delete to set this action up and then
redirect to another URL with a GET which asks for confirmation based
on the previous setup and then POSTs to delete. This keeps it RESTful
in the sense of one U
Actually, the confirmation page is not accessed via a GET. Using the
admin's auth model as an example: the user does a GET to something
like www.example.com://admin/auth/user to get a list of users. Then
they checkmark the users they want to delete, select the "delete"
action, and then click on "
I'm not entirely sure whether you're asking one question or two here.
Firstly, I think that in the RESTful sense, there's nothing wrong with
having a confirmation page that uses the same URL to perform an action
*providing* the HTTP verb is different. In this case the confirmation
page is accessed
I have an app that is modeled after the django admin app. In general
it seems to me that the admin app is RESTful. However, I am
encountering a situation that is similar to the admin apps delete
confirmation process, and I'm curious if anyone out there could
comment on whether this particular par
6 matches
Mail list logo