- From: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
- Date: Wed, 12 Dec 2012 17:15:14 -0500
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: public-ldp-wg@w3.org
- Message-Id: <16F51222-FB24-45C7-B27B-AA5CDAD67BFB@openlinksw.com>
On Dec 12, 2012, at 08:50 AM, Andy Seaborne wrote: > It would be great if it were included but the issues of what is being PUT (content handled differently to PUT of a resource\container) or POST to a service (not REST) do need to be covered. This may be thought tangential, but I think it relevant. I grow increasingly tired of the suggestion and even assertion that HTTP POST is inherently not RESTful. This is not so. I refer you to... 1. Wikipedia: Representational State Transfer <http://en.wikipedia.org/wiki/Representational_state_transfer> 2. Roy T. Fielding: "It is okay to use POST" <http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post> 3. FileCatalyst (Marcel): "REST – HTTP POST vs. HTTP PUT" <http://www.filecatalyst.com/rest-http-post-vs-http-put> 4. Steve Klabnik: "Nobody Understands REST or HTTP" <http://blog.steveklabnik.com/posts/2011-07-03-nobody-understands-rest-or-http> Frustratedly yours, Ted -- A: Yes. http://www.guckes.net/faq/attribution.html | Q: Are you sure? | | A: Because it reverses the logical flow of conversation. | | | Q: Why is top posting frowned upon? Ted Thibodeau, Jr. // voice +1-781-273-0900 x32 Senior Support & Evangelism // mailto:tthibodeau@openlinksw.com // http://twitter.com/TallTed OpenLink Software, Inc. // http://www.openlinksw.com/ 10 Burlington Mall Road, Suite 265, Burlington MA 01803 Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Wednesday, 12 December 2012 22:15:45 UTC