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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|