Java201.com

• A RESTful Core for Web-like Application Flexibility - Part 1 by Tom Hicks, Randy Kahle   - [Clicks: 2]
  Representational State Transfer (REST) computing offers developers and applications a number of advantages, including simplicity and flexibility in running applications. Tom Hicks and Randy Kahle begin this series on RESTful computing with the surprising topic of binding.
  http://www.theserverside.com/tt/articles/article.tss?l=ARESTfulCorePart1 - Jul, 2008
• REST Anti-Patterns by Stefan Tilkov   - [Clicks: 1]
  In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
  http://www.infoq.com/articles/rest-anti-patterns - Jul, 2008
• Describe REST Web services with WSDL 2.0 by Lawrence Mandel   - [Clicks: 3]
  At their core, Web services define a mechanism for machine-to-machine interaction using a network and XML. A key component of a Web service is a formal description with Web Services Description Language (WSDL). Until recently there was no formal language to describe REpresentational State Transfer (REST) Web services—now there's WSDL 2.0. This article introduces you to REST and WSDL 2.0, and walks you through creating a WSDL 2.0 description of a REST Web service.
  [Includes sample code]
  http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/index.html - May, 2008
• RESTful Services with Erlang and Yaws by Steve Vinoski   - [Clicks: 3]
  In this article, Steve Vinoski explains how to build RESTful Web services using the Erlang programming language and the Yaws web server. While Steve considers most Web frameworks failures simply because they were a poor match to the problem, he believes Yaws and Erlang are a better match for RESTful development than many other language frameworks that were built specifically for that purpose.
  http://www.infoq.com/articles/vinoski-erlang-rest - Mar, 2008
• Addressing Doubts about REST by Stefan Tilkov   - [Clicks: 3]
  Invariably, learning about REST means that you’ll end up wondering just how applicable the concept really isbeyond introductory, “Hello, World”-level stuff. In this article, Stefan Tilkov addresses 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services.
  http://www.infoq.com/articles/tilkov-rest-doubts - Mar, 2008
• RESTful SOA using XML by Adriaan de Jonge   - [Clicks: 8]
  Service Oriented Architecture usually implies heavyweight technology for large enterprises. The advantages of the SOA architectural pattern also apply to smaller environments. To follow SOA principles, you don't necessarily need all the overhead that is useful in larger environments. You can use lightweight principles like REST to do so. This article describes how.
  [Includes sample code]
  http://www.ibm.com/developerworks/xml/library/x-restfulsoa/index.html - Feb, 2008
• Hypermedia in RESTful applications by Mark Baker   - [Clicks: 10]
  One of the constraints defined for the architectural style known as REST is "hypermedia as the engine of application state". Mark Baker, well-known for being one of the first who advocated the REST style instead of the mainstream web services approach, discusses that the hypermedia constraints means in practice and why it is essential to RESTful design.
  http://www.infoq.com/articles/mark-baker-hypermedia - Jan, 2008

[Top]