REST in practice : hypermedia and systems architecture (edit title/settings)

Ridiculously Simplified Synopsis edit

Write a ridiculously simplified synopsis.

Characters/People edit see section history

• Uris: Add a description of this character.
• Richardson

Quotes edit see section history

• “The DSL used for the Restbucks hypermedia framework is a state machine description markul language.”

• Popular Highlights from Kindle Customers

• Robust services obey Postel’s Law,[29] which states, “be conservative in what you do; be liberal in what you accept from others.” That is, a good service implementation is very strict about the resource representations it generates, but is permissive about any representations it receives.

  Highlighted by 19 Kindle customers

• On each interaction, the service and consumer exchange representations of resource state, not application state.

  Highlighted by 18 Kindle customers

• Use POST to create a resource identified by a service-generated URI. Use POST to append a resource to a collection identified by a service-generated URI. Use PUT to create or overwrite a resource identified by a URI computed by the client.

  Highlighted by 18 Kindle customers

• Using content negotiation, consumers can negotiate for specific representation formats from a service. They do so by populating the HTTP Accept request header with a list of media types they’re prepared to process.

  Highlighted by 17 Kindle customers

• Once we understand that the states of a process can be modeled as resources, it’s simply a matter of describing the transitions between those resources and allowing clients to choose among them at runtime.

  Highlighted by 16 Kindle customers

• URI tunneling isn’t web-friendly because URIs are used to encode operations rather than identify resources that can be manipulated through HTTP verbs.

  Highlighted by 15 Kindle customers

• PUT expects the entire resource representation to be supplied to the server, rather than just changes to the resource state.

  Highlighted by 14 Kindle customers

• The relationship between URIs and resources is many-to-one. A URI identifies only one resource, but a resource can have more than one URI.

  Highlighted by 13 Kindle customers

• This separation between a resource and its representations promotes loose coupling between backend systems and consuming applications. It also helps with scalability, since a representation can be cached and replicated.

  Highlighted by 12 Kindle customers

• Resources are the fundamental building blocks of web-based systems, to the extent that the Web is often referred to as being “resource-oriented.” A resource is anything we expose to the Web, from a document or video clip to a business process or device.

  Highlighted by 11 Kindle customers

Setting & Locations edit see section history

• Rome
• Jersey
• Http

Authors & Contributors edit see section history

1. Savas Parastatidis (Author)
2. Jim Webber
3. Ian Robinson

Classification edit see section history

• Library of Congress: Add the Library of Congress Classification.
• Dewey: 005.276

Subjects edit see section history

• Books › Computers & Internet › Programming › Software Design, Testing & Engineering › Software Development
• Books › Computers & Internet › Hardware › Design & Architecture

Links to Supplemental Material edit see section history

• REST in Practice