I think the idea is to embrace the value of the HTTP methods (the standard) even in an imperfect world. So, while IE might not support a form with method "PUT", we can provide a band-aid that will let a non-compliant browser work while offering seemless functionality for browsers that do.
jll On Apr 12, 11:09 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 4/12/07, Jesse Lovelace <[EMAIL PROTECTED]> wrote: > > > I've been interested in the idea of faking HTTP methods that > > browsers/servers might not support > > I'm not sure I understand the motivation to munge the request from the > browser to use different verbs. Surely if you're inspecting a > particular value in the form request, you're coupling the server and > client, and therefore the POST/PUT semantic difference is moot? You > might as well make it POST -> FROBNITZ, no? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
