| >In any case, if you find REST restrictive, fine, go ahead and do your RPC. Just don't try to tell me that it's anything other than RPC, with all the problems and warts we all know. Sorry, did Computer Science change the last few years and RPC went out of style? What "problems and wars we all know" RPC has? Nothing that doesn't go with the field, and isn't already the same (or worse) in REST. RPC is a basic CS notion that will always be around -- the same way garbage collection, floating point math, functional programming, regular expressions, etc will be. It not some faulty fad that went away. >The value in REST is exactly that it forces you to simplify your interface down to basic verbs that everyone can understand and work with It just forces you to overload HTTP verbs, verbs that people don't use in the first place (even web developers knew and used GET and POST but not PUT and DELETE -- outside of REST and some specialty domains that is), that might or might not match your business logic. >From that point of view, something like SOAP is a perfectly respectable protocol and you should use that instead. Slippery slope fallacy. |