RESTful services without the sweat
Representational state transfer (also known as REST, baby) is an approach to designing loosely coupled applications that rely on named resources rather than messages. As it turns out, the most involved part of building a RESTful application is deciding on the resources you want to expose. Once you’ve done that, building RESTful Web services a snap, especially if you use the Restlet framework, which greatly simplifies the task of defining and implementing RESTful services.
Check out IBM developerWorks‘ tutorial dubbed “Build a RESTful Web service“– in it, you’ll get to know what REST is and how to build RESTful applications with Restlets, plus, you’ll see how to deploy and test them while you are at it!
| Related odds and ends | ||
|---|---|---|
7 comments Tuesday 22 Jul 2008 | Articles
7 Responses to “RESTful services without the sweat”
[...] bookmarks tagged restful RESTful services without the sweat saved by 5 others Ruyana bookmarked on 08/12/08 | [...]
[...] as anyone who has ever pondered REST and the hip implications of implementing RESTful applications knows, the question that often pops up is: Is this URI [...]
[...] – bookmarked by 3 members originally found by lizblankenship on 2008-10-08 RESTful services without the sweat http://thediscoblog.com/?p=230 – bookmarked by 6 members originally found by sailorpeach on [...]
[...] that for easy, man? The next time you need to interact with a RESTful web service, consider using Groovy’s HTTPBuilder — it’s a [...]
[...] times with RESTful services, a particular URI might need a further level of detail than simply /widget/id — that is, a [...]
Hi andy, i found youre tutorial on restful web services interesting. But it seems like the RaceDAO class in the limrick-0.1.jar is not up to date with the tutorial document. The findall method is missing or am i missing something, i know the tutorial is from last year but i thought id ask.
thanks,
Johannes
Hi Johannes — what’s the exact issue? Or which code example are you working on?