So basically, it's just REST, no?
Exactly. Well, not quite *exactly* {grin}. One of the tenants of REST that I'm not comfortable is the HTTP method mappings. For instance I'd be more comfortable having insert and update combined into POST rather than PUT, or separating them respectively out into PUT and POST. Forgive me if I'm combining ideas from the REST wiki and the dissertation, I'm still on my first cup of coffee {grin}.

I'm sure if I had time to go back and re-read Fielding's dissertation I could come up with a few more ways that what's proposed in the original post isn't exactly REST, but his work was certainly one of the inspirations for this proposed method.

-- Douglas Hunter

In reply to Re: Re: Re: Re: [OT] Desktop applications over HTTP by dug
in thread [OT] Desktop applications over HTTP by dug

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.