links.lmorchard.com - #post

PUT or POST: The REST of the Story « Open Sourcery

Sun, 20 Jun 2010 03:53:09 +0000

Tags: #http #post #put #rest #webdev

PUT vs POST in RESTful Web Service « vincenthome’s Tech Clips

Fri, 26 Dec 2008 20:13:46 +0000

"This explains when to use POST or PUT for creating new resources. The answer ultimately lies in who is responsible for determining the new resource’s URI. If the client is in charge, the client can use PUT to the new URI (like we did for user accounts) and the service can return a response code of 201 (“Created”). However, if the service is in charge of generating the new URI, the client should POST the new resource to a factory URI like we’ve done for bookmarks. Then, the service can return a response code of 201 (“Created”) along with the URI of the new resource in the response “Location” header."

Tags: #http #post #put #rest #webdev

Django snippets: minimal nginx conf to split get/post requests

Wed, 15 Oct 2008 19:37:44 +0000

"After a point the sql server becomes the bottleneck in lots of web application, and to scale, master-slave replication with single master, multiple slave is recommended. This setup with nginx can be used to accomplish traffic distribution between master and slave based on request method. "

Tags: #config #get #http #master #nginx #post #scalability #slave #sysadmin #webdev

Why PUT and DELETE?

Fri, 29 Dec 2006 22:14:00 +0000

"In this interview, Elliotte Rusty Harold discusses the true meaning of PUT and DELETE."

Tags: #delete #get #http #post #put #rest #webdev