JavaZone 2009 - Ditch your complex clients: become RESTful
This presentation will outline how Escenic went from an RPC based approach to a RESTful webservice. The presentation will cover the design of both the web service and the client. We will list lessons learned through the project and how these lessons have affected the end result.
You will not NOT learn anything about the jungle of RESTful frameworks, as they are only tools to get the job done. You will learn the principles of REST and how it affects client side programmers.
The focus will be on how to build the server and client correctly according to the principles behind REST, and not misuse the term as Flickr, SocialSite and Amazon do. RESTful HTTP is more than just using HTTP: it is identifying resources using URIs, exposing relationships between resources, and manipulating resources using the semantics of HTTP verbs. It also means designing resources to fit the constraints, based on nouns (and sometimes verbs) of the domain
Erlend Hamnaberg
Systems developer at Escenic AS. He has worked at Escenic for two years and has worked with both RESTful server and client applications. His technical interests revolve around HTTP, REST, Dependency Injection, database abstractions, Swing, Java and Scala.
In his spare time he is a member of the the JavaZone conference program comitee and he is also the lead developer and architect behind the open source HTTP-cache library HTTPCache4j.
Erik Mogensen
Chief Architect at Escenic AS. He has worked at Escenic for nine years and has worked with the server and client software all this time. He introduced REST to the company in 2004 and has designed most of the company's RESTful applications.