This link has been bookmarked by 31 people . It was first bookmarked on 04 Apr 2008, by Matthias Käppler.
-
07 Mar 13
-
On the face of it, this appears a perfectly RESTful, hypermedia based solution, very similar to how an HTML form (or URI Templates) is used. So what's the caveat? It's the issue of when the WADL is consumed. Some Web services proponents who have taken an interest in Web based solution have been using WADL as they would use WSDL, as a design-time artifact. Using WADL this way though, is akin to developing a Web browser with built-in knowledge of, say, the Google homepage HTML form at the time the browser was compiled: if Google changes the form in a backwards-incompatible way (i.e. not just adding a new optional parameter) after the browser is deployed, then the browser will not be able to use that resource/service. Using the hypermedia constraint with WADL means that the client should consume the WADL at runtime. So be careful when choosing your WADL tooling, as some tools that try to help you, don't.
-
-
07 Jan 13
-
12 Sep 12
-
A hypermedia solution would have used standardized identifiers - URIs, for the Web - instead of proprietary ones, thereby avoiding the need for Flickr-proprietary knowledge for a client to go from a document with a list of people, to a document about one of those people.
-
standardized
-
-
28 Nov 11
-
18 Nov 11
-
26 Sep 11
-
14 Jan 10
-
03 Dec 09
-
REST architectural style
-
's most important constraint, the uniform interface, in particular the aspect of that interface that constrains the methods that can be invoked on resources.
-
there's quite a bit more to the uniform interface than that
-
a sub-constraint
-
arguably the most important constraint of REST in the sense that it alone provides the bulk of the "shape" of RESTful systems as we know them.
-
Hypermedia as the engine of application state
-
So by using a common application model, one that is not just standardized, but fixed for all time, you are reducing coupling between consumer and producer by permitting each to evolve independently of the other
-
-
11 Nov 09
-
17 Apr 09
-
16 Apr 09
ken .short and simple example putting some meat on Roy's famous thesis - example from flickr, the "nsid" returned from the contacts.getlist api - "But once a client has retrieved that document, then what?" - wrapping up the internal-id with a standard, univers
data flickr hypertext knowledge principles programming rest simplicity web
-
25 Mar 09
-
09 Jan 09
-
23 Aug 08
Alan DeanChances are that if you've heard of the REST architectural style, that you've also heard about what some consider it's most important constraint, the uniform interface, in particular the aspect of that interface that constrains the methods that can be inv
-
29 Jul 08
-
05 Mar 08
Flickr's current approach of requiring that clients possess Flickr-specific knowledge in order to progress from one application state to another, is simply another way of saying that they have a proprietary application model. Not only is it proprietary th
hypermedia API REST architecture http Web Services Flickr web développement
-
07 Feb 08
-
31 Jan 08
-
30 Jan 08
-
29 Jan 08
-
28 Jan 08
Chris JoblingArticle that gives a useful perspective on the use of hypermedia for capturing state transitions in a RESTful architecture.
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.