#webservices

93 bookmarks tagged with #webservices · RSS Feed · ← All Tags

I finally get REST. Wow. - The Tripping Point - Pluralsight Blogs

http://www.pluralsight.com/community/blogs/tewald/archive/2007/04/26/46984.aspx
"The essence of REST is to make the states of the protocol explicit and addressible by URIs. The current state of the protocol state machine is represented by the URI you just operated on and the state representation you retrieved. You change state by operating on the URI of the state you're moving to, making that your new state. A state's representation includes the links (arcs in the graph) to the other states that you can move to from the current state. This is exactly how browser based apps work, and there is no reason that your app's protocol can't work that way too."

The Wonderful World of Web Hooks // Notebook // Kyle Slattery

http://kyleslattery.com/notebook/entries/the-wonderful-world-of-web-hooks
"The aspect that excites me the most is how easy it is to write a web hook. All you need to have is a cheap PHP host and some basic knowledge about handling POST data, and you're ready to go. By shortening the learning curve, web hooks make it possible for more people to build on top of existing platforms, leading to a more connected and interesting internet."

REST APIs must be hypertext-driven » Untangled

http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
"What needs to be done to make the REST architectural style clear on the notion that hypertext is a constraint? In other words, if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period. Is there some broken manual somewhere that needs to be fixed?"

ongoing · Learning REST

http://www.tbray.org/ongoing/When/200x/2008/10/01/Learning-REST
"I was talking to a colleague who has to become savvy in a hurry about modern Web applications and he asked “How do I learn about REST?” Good question. I thought of a couple of suggestions, then asked Twitter and got some more. Here they are."

Dare Obasanjo aka Carnage4Life - Explaining REST to Damien Katz

http://www.25hoursaday.com/weblog/2008/08/17/ExplainingRESTToDamienKatz.aspx
"At this point, the benefits of building RESTful services for the Web should be self evident. The Web has a particular architecture and it makes sense that if you are deploying a service or API on the Web then it should take advantage of this architecture instead of fighting against it. There are millions of deployed clients, servers and intermediaries that support REST and it makes sense to be compatible with their expectations. "

"High" REST [@lesscode.org]

http://lesscode.org/2006/03/19/high-rest
"GET/POST/PUT/DELETE advocates who claim they are pointing out the obvious are actually making a religious argument, and that poor thesis is playing the role of C-3P0 in the Ewok village. It's unproven technology, and it should be viewed with healthy skep