On Jan 29, 2008 11:15 AM, Ian Bicking <[EMAIL PROTECTED]> wrote: > I think using POST is okay; if you are using _action=PUT it isn't a PUT > anyway, and it feels like it's not much more than HTTP verb push-ups. > POST over a resource updates the resource in some fashion; updating a > resource in-place via POST is okay (PUT might be better, but > not-really-a-PUT *isn't* better).
I generally agree with you, and I keep going back and forth whether to use map.resource in my own applications. Because what does it really matter if you use POST or PUT? Users can't effectively predict URLs across applications anyway, and there's no practical reason to; e.g., no Google GWebsite that's a common front end for interacting with a variety of sites. "/resource/" vs "/resource/1" is a good idea, but I'm not sure the rest of it matters. Are there any other practical arguments for a REST-like add/edit/delete, or is it all just academic ideology? But still, something needs to be done for Pylons, and map.resource exists, so I guess a fair number of people are using it. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
