News for hackers. Stuff that matters.
Re:The S stands for Simple by InclinedPlane on Tuesday December 15, 2009 @03:00AM (#996133)
Not just JSON and HTTP but specifically REST w/ JSON. There's a lot to be said for such a model.
Re:The S stands for Simple by garnet7 on Tuesday December 15, 2009 @12:43PM (#996953)
What's the difference between "JSON in GET/POST" and "REST with JSON"?
Re:The S stands for Simple by JulianMorrison on Tuesday December 15, 2009 @04:54PM (#997538)
In one, you are essentially doing RPC: here's the input, do the operation and give me an output. In the other, you are remotely manipulating "documents". Even a command to act consists of emplacing a "request" and being redirected to a "response". You navigate between "documents" by following URLs in links.

To be honest, I like REST for CRUD of things that are natural resources, but I think it's wasted extra work for operations that are natural RPCs.

Re:The S stands for Simple by garnet7 on Wednesday December 16, 2009 @12:53PM (#999283)
Ah thanks. Just plain JSON RPC sounds simplest to me.
Re:The S stands for Simple by carey on Tuesday December 15, 2009 @02:36PM (#997195)
"REST with JSON" should send the (relative) URL for the next request, not just an ID. Although there's more to it than just that.