You're quite right about all of that, and I have applied those principles to my REST interface at work. But I didn't say the examples for the OP were REST :-)
CGI::Application::Dispatch has some extra features to make REST easier to implement (by attaching the HTTP verb to the runmode name, so you'd have page_GET, page_DELETE etc. as the real run modes, dispatched from the single /page url). I don't think it's relevant to the OP's question though, and would probably confuse the issue.
By the way, I really, really like the REST approach. It encourages a clear, uncluttered implementation on the backend, and it's very simple to integrate the resulting resources into other applications. Compared to SOAP, REST is a lot cleaner ;)
I also found the columns on xml.com helpful in gaining a more practical understanding of the REST philosophy.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.