Alex Milowski wrote:
E.g. for delete, it would be
POST /member-uri HTTP/1.1
Host: example.org
Method: DELETE
In the entry you'd have:
<atom:link rel="delete" href="/member-uri/delete"/>
Then you'd do a GET, which is much like a DELETE in that an entity body
is not sent. Certainly a 200 with no content is an acceptable resposne.
Blech! :-) Doing a delete with a get is not a particularly safe way to
build an app. [1]
[1]http://www.37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php
Here, you'd have an 'update' relation:
<atom:link rel="update" href="/member-uri/update"/>
Then you'd POST the content but as a it is a different URL, the server
"knows" what to do.
Requiring additional URI's for each operation is a mess.
Certainly, for a client, supporting one is simplest. But, choosing
the right URL amongst a couple different link elements isn't
that hard to implement. And you don't need to set special
headers--which might present problems in certain limited programming
environments.
It's not hard to implement but it's entirely unnecessary. There are
easier solutions. APP is already doing stuff with HTTP headers (Title,
Location, etc), what's one more? ... especially in an optional extension.
- James
