Re:REST API Best Practices
by roryokane on Saturday May 05, 2012 @09:04PM
(#3933777)
This site is a good idea, but right now it's not very good for a REST beginner, as the label "tutorial" would imply. The quick tips are for people who already know REST design. The status codes are for reference only. The HTTP methods are half-tutorial, half-reference, and don't give you any idea of what to do next.
The "eCollege Best Practices guide" under Resources looks good - that's what I want to see from a tutorial. But why is it only in PDF form? You have a website already, and I don't see any tricky layouts in the PDF - why not just put the text in HTML pages? That would lower the barrier of entry to starting reading, make the book easier to read on small screens by allowing you to adjust the page size and font size, make linking to the book easier, and probably have other benefits.
Re:REST API Best Practices
by democracy on Sunday May 06, 2012 @12:53AM
(#3934206)
but itβs incredibly difficult to consume SOAP if you have to develop a client library from scratch, access it via a Web UI, or do anything non-standard.
Is it really incredibly difficult to consume SOAP? I thought any language out there these days can generate the client code from the WSDL.
PUT is most-often utilized for update capabilities, The POST verb is most-often utilized for creation of new resources.
I was under impression people prefer to use POST for updates and PUT for inserts in their REST services...
Nice tutorial though, also a section on security problems and different approaches would be a good article to see there...
Re:REST API Best Practices
by unhappyhippie on Saturday May 05, 2012 @09:09PM
(#3933788)
Apologies for being off-topic, but what's the deal with the url? restapitutorial.com links to an unclaimed page with GoDaddy advertisement whereas www.restapitutorial.com goes to the OP's page.
The "eCollege Best Practices guide" under Resources looks good - that's what I want to see from a tutorial. But why is it only in PDF form? You have a website already, and I don't see any tricky layouts in the PDF - why not just put the text in HTML pages? That would lower the barrier of entry to starting reading, make the book easier to read on small screens by allowing you to adjust the page size and font size, make linking to the book easier, and probably have other benefits.
Is it really incredibly difficult to consume SOAP? I thought any language out there these days can generate the client code from the WSDL.
PUT is most-often utilized for update capabilities, The POST verb is most-often utilized for creation of new resources.
I was under impression people prefer to use POST for updates and PUT for inserts in their REST services...
Nice tutorial though, also a section on security problems and different approaches would be a good article to see there...