XML.com: Constructing or Traversing URIs? - The Diigo Meta page

• 22 Jun 10
  

  Pedro Ângelo

• 21 May 08
  

  owen walton

  rest uri xml webservices api programming

• 21 Mar 08
  

  l.m orchard

  rest webdev webservices ws xml

• 02 Sep 07
  

  Bill D

  uri webservices article architecture rest

• 02 Aug 07
  

  Mats Svensson

  REST programming webdev

• 18 Apr 07
  

  Julian Elve

  webservices/rest

• 23 Jan 06
  

  mallipeddi

  REST web-services tutorial xml web architecture article design dev

• 29 Nov 05
  

  Dan Creswell

  rest soa

• 27 Jul 05
  

  jyap808

  api xml web services rest python del.icio.us uri

• 05 Jun 05
  

  Alan Dean

  Here is a quick review of where we ended in the last column. We answered all four questions about our resources and their representations.

  REST URI Joe.Gregorio

• 26 Apr 05
  

  Nick Gall

  Excellent examples of how to use hypermedia, which IMO can include XML, ad the "engine" of application state.
  

  via_delicious_20101217 ImportedFurl20071006 WebArchitecture-REST pinboardimport20141106 REST Architecture

  • We didn't get here by mistake. "REST is defined by four interface constraints: identification of resources; manipulation of resources through representations; self-descriptive messages; and, hypermedia as the engine of application state." [Roy Fielding] As you can see, when exposing our service to the world we have a range of methods we can use, from URI Construction to Hypertext Navigation, with "hypermedia" like HTML forms filling in the range between those two extremes. Note that while HTML only does URI construction on the query parameters, we don't need to constrain ourselves to just that part of the URI. We could come up with our own URI construction, one that included constructing not just the query parameters but also the path portion of the URI. Let's do that.
• 24 Apr 05
  

  Jason May

  REST

• 08 Apr 05
  

  Rumbero 2010

  REST HTTP URIs

• 

  Sean McBride
• 07 Apr 05
  

  D U

  XML URI develop del.icio.us

• 

  koranteng

  Joe Gregario continues his REST exploration with his bookmark service

  web technology REST design architecture resource modeling resourcemodeling uri http

• 

  znarfor

  Joe Gregorio's latest XML.com column. "Of the four interface constraints of REST, the last one, 'hypermedia as the engine of application state', is the least utilitzed. This article builds the concept from the ground up, and then applies it to the design

  rest web_services social_bookmarking imported

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.