The Source for Java Technology Collaboration
User: Password:



Erik Hatcher

Erik Hatcher's Blog

Taking a REST

Posted by erikhatcher on June 10, 2003 at 05:17 PM | Comments (3)

Styles of Integration: REST Versus Web Services Architecture

Paraphasing, this is the quote that stuck out from this presentation: REST architectures tend to be resilient to changes.

I must admit to being much more fond of the REST side of things. URL's matter to me. I'm mainly speaking about URL's that users see - they should be elegant and meaningful. For computer to computer URL's and Web Services, its a different story.


Bookmark blog post: del.icio.us del.icio.us Digg Digg DZone DZone Furl Furl Reddit Reddit
Comments
Comments are listed in date ascending order (oldest first) | Post Comment

  • All URLs matter
    It's not just the one's that users will see. The programmers will have to deal with URLs and they will calcify those URLs into programs and programs are notoriously less resilient than people.

    Posted by: johnm on June 24, 2003 at 09:09 AM

  • I know this is a really old blog but I've only just started investigating REST and thought I should make this comment:

    You talk about "REST Versus Web Services Architecture", but I believe, from my readings on the subject, that REST IS a web services architecture. In fact, a lot of people are annoyed that M$ and IBM have made the term "web services" equivalent with SOAP, when this should not be the case. That's the impression I've gotten, anyway: that REST is a different (non-RPC) architecture for implementing web services.

    Posted by: grlea on February 24, 2005 at 04:17 PM

  • goos article. very infomative. the comments put the stuff into perspective.
    order taking

    Posted by: ordertaking on October 02, 2006 at 08:00 AM





Powered by
Movable Type 3.01D
 Feed java.net RSS Feeds