Through Stefan Tilkov’s blog, I came across ServiceReg whose goal is to let us "execute RESTful web service calls against Rails applications (and other REST compliant framworks) with a simple URL". The "simple URL" is one that can be submitted via a GET.
If I have a resource at http://www.subbu.org/vide/1234 that can be updated via a PUT, ServiceReg will turn that into a GET:
http://servicereg.com/put/subbu.org/video/1234?title=Hello
This is bizarre. Why proxy POST, PUT and DELETE via a GET? As Stefan pointed out, this violates the purpose of RESTful design. But there is more to it. It masquerades all write operations as read operations, and that could lead to unintended consequences.
The motivation of ServiceReg may be to let GETs be used to replace other verbs so that URLs can be bookmarked. But still – it does not make sense.
