Pebbling Club 🐧🪨

  • PUT or POST: The REST of the Story Ā« Open Sourcery
    Feed
    Embed
    Unfurl
  • PUT vs POST in RESTful Web Service Ā« vincenthome’s Tech Clips
    Notes
    "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."
    Feed
    Embed
    Unfurl
  • Django snippets: minimal nginx conf to split get/post requests
    Notes
    "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. "
    Feed
    Unfurl
  • Why PUT and DELETE?
    Notes
    "In this interview, Elliotte Rusty Harold discusses the true meaning of PUT and DELETE."
    Unfurl