On Oct 5, 10:43 am, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> >  * Does django.views.generic.utils.coerce_put_post() indicate a change
> > that needs to be made in Django? (Is there an existing ticket for
> > this?)
>
> Yeah, this has been a wart in Django for a while -- Django doesn't
> really "get" PUT very well. Along the same lines,
> request.raw_post_data is terribly named. I don't know that there's a
> single ticket anywhere, but I'd like to see a general cleanup here.
>
> I don't see this as a blocker for class-based views, though: we have a
> narrow feature deadline that I'd like to hit, and then a longer
> bug-fix period we can use to clean up PUT/POST and such.

I just wanted to underline what most people here already know: that
according to the html 4 spec [1], the only acceptable values for
form's method attribute are GET and POST.  Also, in common practice,
PUT is used primarily in making ajax calls, or in accessing
programatic JSON or XML APIs, not in html forms.  HTML5 does specify
PUT as a possible value for that attribute, but if you are planning on
improving your support of PUT, I have to believe that it is
*primarily* because you want to improve the ability to implement
programatic APIs in Django.

However, as I have detailed in my last two posts in this thread, the
current implementation, lacks any ajax/json/xml support.  In those two
posts I have detailed possible modifications to the code that would
allow ajax support to be introduced.  I think that Andrew Godwin's
remarks contribute quite a bit to that discussion, but no one else
responded yet.  This is something that needs to be tangibly addressed.

I am worried that with the pace that things are going here that ajax
support may be ignored, or just pasted-on at the last minute.
Clearly, you see this as an important feature, or you wouldn't be
considering improving PUT support, and wouldn't be supporting the
DELETE verb.  If ajax/json/xml are to be supported by the generic view
classes, however, some refactoring has to be made to the code.

[1] http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.3

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to