REST Client Implementation Embracing HATEOAS Constraint? -
Is anyone aware of the implementation of the rest of the client who embraces the hazard of haytes?
It seems that this is a good candidate, the way it has been documented and the Ruby, Java and Python implementations are in the works but I have not found any code code yet.
I see anything - even a partial implementation will be useful.
The first thing you should look like is a common web browser. This is the standard for the client who embraces the hethes (at least to some extent).
Hypermedia works It's so easy that it's almost painful:
- You can change your browser to
http://pigs-are-cool.org/ Enter
- Browser loads HTML pages, images, CSS and so on.
- At this point, the app (your browsing experience) is on a specific URI.
- The browser is showing the content of that URI
- You see a link in the app
- You click the link
- The browser follows this link
- At this point, the application is different URI
- The browser is showing the contents of the new UI >
- HyperMidia = HTML page with embedded link
- Application Status = Any time in the browser What are you looking for
So Hateys really describes what happens in the web browser when you visit a web page from a web page:
Embedded link Drive can you see in the browser at any time
The term HATEOAS is just an abstract of this browsing experience.
Other examples include cool client applications:
- RSS and feed readers exceed the links given by users
- Most atompob blogs Clients only require one URI in the services documentation, and from there it shows where to upload images and blog posts, search and so on.
- Perhaps Google Gadgets (and similar), but they are only browsers in different skin.
- Web crawlers are also cool customers, but they are a niche market.
Features of some specific client software:
- Customer works with any server, given that it started with some URIs And the server responds to the expected results (such as a nuclear blog client, for an atom's document of documents).
- The client does not know anything about how the server can detect it at runtime, besides the other URI designs
- The customer knows enough media types and this Links to relationships to understand what the server is saying (like Atom or RSS)
- The client uses embedded links to find other resources; Some manually (such as
& lt; a href =
) In addition to a user-operated, and called GoogleBot, "user agents" can be correctly stated.
Comments
Post a Comment