I still don't get it. There have been several things I never got or rather they were so obvious / intuitive to me there was nothing for me to "get". Still I spent years thinking I missed something cause so many others had such problems with them. Pointers & recursion come to mind.
There just doesn't seem that much to REST (that's not a bad thing). Lot's of hype, fud, misunderstanding built up around REST. Arguments over the proper way to apply REST to HTTP/Web. But, REST itself seems sort of duh, how else would you do it?
Many (most?) novel innovations seem obvious and self-evident after the fact. Even rocket science (of course make a pointed tube, fins for stability, and _just_ the right fuel- how else would you do it?)
What is also really good is Richardson and Ruby's "RESTful Web Services" book. They coined the term "Resource Oriented Architecture" to describe a specific REST design implementation and to side-step a religious war on what is and is not REST.
Comments
I still don't get it. There have been several things I never got or rather they were so obvious / intuitive to me there was nothing for me to "get". Still I spent years thinking I missed something cause so many others had such problems with them. Pointers & recursion come to mind.
There just doesn't seem that much to REST (that's not a bad thing). Lot's of hype, fud, misunderstanding built up around REST. Arguments over the proper way to apply REST to HTTP/Web. But, REST itself seems sort of duh, how else would you do it?
It's not magical rocket science, right?
Many (most?) novel innovations seem obvious and self-evident after the fact. Even rocket science (of course make a pointed tube, fins for stability, and _just_ the right fuel- how else would you do it?)
Have you read Roy's dissertation?
I read it and was surprised at how readable I found it (never mind being a dissertation).
http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
What is also really good is Richardson and Ruby's "RESTful Web Services" book. They coined the term "Resource Oriented Architecture" to describe a specific REST design implementation and to side-step a religious war on what is and is not REST.