I'm collecting popular misconceptions about REST. Got some of your own? Please let me know using #notrest. I'll follow up with a few.

Feb 27, 2013 · 3:34 PM UTC

28
9
4
Load newest
Replying to @stilkov
@stilkov Not sure what you're looking for but IMO the idea that REST is "better" or "more powerful" than RPC is misguided. #notrest
1
@rolandbouman I don't think it's a misconception that REST is “better” than RPC (depending on what you mean by RPC, of course)
3
more replies
Replying to @stilkov
@stilkov You can implement RESTful APIs using only GET, so long as you have predictable URLs. #notrest
1
1
@robsmallshire Wow, that's a good one.
Replying to @stilkov
The only way how to build APIs is doing it RESTful.
Replying to @stilkov
@stilkov for things beyond basic #CRUD, you "run out of methods and have to invent new ones." #notREST
1
Replying to @stilkov
@stilkov documenting #REST means creating "site maps", instead of providing entry points and document discoverability. #notREST
1
Replying to @stilkov
@stilkov there has to be an automated way how i can simply take my procedural API and RESTify it mechanically. #notREST
1
Replying to @stilkov
@stilkov it's ok to look at a link #URI and "predict" what an interaction is about, and then implement special client behavior. #notREST
Replying to @stilkov
@stilkov REST=CRUD for services : POST=create, GET=read, PUT=update, DELETE=delete #notrest
4
2
Load more