Hyper fantasy
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Hyper fantasy

  • 1,146 views
Uploaded on

From Manchester Geek Nights (http://upcoming.yahoo.com/event/6718576/MCR/Manchester/Hyper-Fantasy-Choose-your-path-through-the-world-of-REST-using-Restfulie/Kilburn-Building)...

From Manchester Geek Nights (http://upcoming.yahoo.com/event/6718576/MCR/Manchester/Hyper-Fantasy-Choose-your-path-through-the-world-of-REST-using-Restfulie/Kilburn-Building)

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,146
On Slideshare
1,146
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
5
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Ask audience if they want to see code or app first

Transcript

  • 1. Hyper Fantasy
    Adventures In Hypermedia
    Jim Barritt
  • 2. Prologue
    REST – Roy Fielding
    REST IN PRACTICE – Jim Webber, Ian Robinson, Savas Parastatdis
    RESTFULIE – Guilherme Silveira, Lucas Cavalcanti
  • 3. Love to <Link>
    Hypermedia Controls
    <atom:link href=“” rel=“” />
    <a href=“” rel=“” >Link to somewhere</a>
    Media types
    application/xhtml+xml
    text/html
    application/xml
    application/json
    application/vnd.restbucks+xml
  • 4. Talking in Http
    HEAD GET PUT POST DELETE
    200 (ok)
    404 (not found)
    500 (internal error)
    418 (I’m a teapot)
    http://www.faqs.org/rfcs/rfc2324.html
    Accept: text/* application/xml
  • 5. RESTafarianism
    Client-Server
    Stateless
    Cacheable
    Layered System
    Uniform interface
    Identification of resources
    Manipulation of resources via representations
    Self-descriptive messages
    HATEOAS (Hypermedia as the engine of application state)
    Code on demand (optional)
  • 6. Restfulie
    Why would I use restfulie?
    1. Easy —> writing hypermedia aware resource based clients
    2. Easy —> hypermedia aware resource based services
    3. Small -> it’s not a bloated solution with a huge list of APIs
    4. HATEOAS —> clients you are unaware of will not bother if you change your URIs
    5. HATEOAS —> services that you consume will not affect your software whenever they change part of their flow or URIs
  • 7. Hyperia
  • 8. To the CODE!
  • 9. Epilogue
    http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
    http://www.facebook.com/RESTinPractice
    http://github.com/caelum/restfulie-java
    London geek night 22nd November
    http://github.com/jimbarritt/spikes/tree/master/restfulie/