The HATEOAS Tumblog
Using an HTML5 microdata theme and featuring HATEOAS content.Â
Mike Driver
Lint Roller? I Barely Know Her
AnasAbdin
he wasn't even looking at me and he found me
d e v o n

Discoholic đȘ©
Show & Tell

JVL
Keni
I'd rather be in outer space đž
TVSTRANGERTHINGS

â

Janaina Medeiros
Xuebing Du
i don't do bad sauce passes
ojovivo
No title available

blake kathryn
No title available
we're not kids anymore.

seen from United States
seen from Spain

seen from Colombia

seen from United States
seen from United States
seen from United States
seen from United States
seen from United States

seen from United States
seen from United States
seen from United States
seen from United States
seen from United States

seen from United States

seen from United States
seen from Spain
seen from United States
seen from United States
seen from TĂŒrkiye
seen from Sweden
@hateoas
The HATEOAS Tumblog
Using an HTML5 microdata theme and featuring HATEOAS content.Â
In this article, Jim Webber, Savas Parastatidis and Ian Robinson show how to drive an application's flow through the use of hypermedia in a RESTful application, using the well-known example from Gregor Hohpe's "Starbucks does not use Two-Phase-Commit" to illustrate how the Web's concepts can be used for integration purposes.
RESTful web services are one of our core design patterns. Fieldingâs thesis identifies four major constraints that identify a RESTful architecture (statelessness, resource-orientation, uniform interface, hypermedia-driven application state). Many âRESTfulâ APIs only get 3 out of 4 of these; weâve begun experimenting with using XHTML as a media type for our APIs, and this provides a lot of power in terms of scalability and loose coupling between client and server.