A while ago I wrote a "web service" of sorts that seems to be something like what's described in the article. It consisted of a cgi script that when asked to do stuff, did it, and returned plain text (Content-type: text/plain). URLs looked like: https://.../foo.pl?do=something&arg1=bar&arg2=baz ('...' replaced by the actual domain). If you asked it for a list of something, results were returned as one item per line. If you asked it to *do* something, it usually returned "OK" or "ERROR".
So, that's all there was. Everything was a GET, the base URL was always the same (just a path to the cgi script, and no equals sign in the path or anything like that), and it was only really used by a dedicated client app -- though you could access it from a browser too, if you cared to (mostly for testing purposes). The client provided the user interface and talked to the cgi script behind the scenes.
Was my method inferior? Everything worked like it was supposed to. In what ways is official "REST" better?
In reply to Re: Developing RESTful Web Services in Perl
by bramble
in thread Developing RESTful Web Services in Perl
by derby
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |