ongoing · REST Questions - The Diigo Meta page

• 22 Aug 08
  

  Olifante *
  • I personally tend to think that schema-driven mapping is
    hopeless, contracts are interesting, registries are a fantasy, and
    payload
    wrappers are very promising.
  • REST, say its aficionados, is more than just HTTP. And that’s true in
    theory. But in practice, there are a whole lot of benefits to just getting
    HTTP right. Suppose just hypothetically that your app violated a bunch of REST
    precepts, say by making heavy use of cookies and never embedding hyperlinks in
    what it sent. But suppose also that it was a really good HTTP citizen;
    getting the caching
    right, not misusing POST, and taking advantage of idempotency where
    possible.
    Well, you know, it might be a pretty good app, and scale startlingly well.
  • 2 more annotations...
  • • statelessness, like many other
      good things (Buddha-nature,
      purely descriptive
      markup) is an Aristotelian virtue; unattainable in an absolute sense, but
      rewarded to the extent you can practice it.
    • I’ve never talked to Roy about
      this, but my perception is that REST was reverse-engineered from his
      understanding of what makes the Web work, based on having been there when some
      of the most important pieces were being built.
• 

  Takuya Homma
• 21 Aug 08
  

  Jonathan Broad

  rest article soap soa restful ffgyi

• 20 Aug 08
  

  Michael Hocter

  REST Development Architecture Article

• 18 Aug 08
  

  Klaus Kämpf

  rest

• 

  takayuki kawamoto

  RESTful soa soap rest

• 

  Brent Sordyl

  Where Are the Tools? Once you get past ActiveResource, Restlet, and Jersey, I’m not aware of much. Seems like an opportunity to me because, you know, REST really actually truly works, as religions go it’s a very practical one.

  webservices restful rubyonrails

• 

  Frank Colcord

  Ruby

Would you like to comment?

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