The HATEOAS Tumblog
Using an HTML5 microdata theme and featuring HATEOAS content.Â

pixel skylines
Xuebing Du
Not today Justin
i don't do bad sauce passes
hello vonnie

will byers stan first human second
$LAYYYTER

Cosimo Galluzzi
noise dept.
he wasn't even looking at me and he found me
Misplaced Lens Cap
DEAR READER

ellievsbear

Love Begins
Cosmic Funnies
Three Goblin Art

Discoholic 🪩

seen from Estonia

seen from T1

seen from United Kingdom
seen from United States
seen from South Korea

seen from Spain
seen from Singapore

seen from Ecuador

seen from TĂĽrkiye
seen from Germany
seen from Italy

seen from Malaysia
seen from United States
seen from Argentina
seen from United Kingdom

seen from United States
seen from Australia

seen from United States

seen from United States
seen from France
@hateoas
The HATEOAS Tumblog
Using an HTML5 microdata theme and featuring HATEOAS content.Â

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
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.