Re: PacePutDelete (was What do we get with PUT/DELETE?)

["Jason Diamond" <jason@xxxxxxxxxxxxx>]

Joe Gregorio said:
>
> In response to the discussion over
> clients that can't support PUT/DELETE
> I have put up a Pace that proposes
> changes to the AtomAPI to accomodate
> such clients.

Maybe I missed this but why not use an extension header as opposed to an
element in the content? That would make it possible for servers to
dispatch to the appropriate handler without having to parse any of the
content.

Alternate DELETE:

POST /path/myLastEntry.atomapi HTTP/1.0
Content-type: application/atom+xml; charset=utf-8
X-WSSE: UsernameToken Username="USERNAME", PasswordDigest="PASSWORDDIGEST",
        Nonce="NONCE", Created="2003-09-08T05:52:36Z"
X-Atom-Method: DELETE

<?xml version="1.0" encoding='utf-8'?>
<entry xmlns="http://purl.org/atom/ns#";>
  <!-- This entry seems rather worthless, doesn't it? -->
</entry>

Alternate PUT:

POST http://example.com/myRecentEntry HTTP/1.0
Content-type: application/atom+xml; charset=utf-8
X-WSSE: UsernameToken Username="USERNAME", PasswordDigest="PASSWORDDIGEST",
        Nonce="NONCE", Created="2003-09-08T05:52:36Z"
X-Atom-Method: PUT

<?xml version="1.0" encoding='utf-8'?>
<entry xmlns="http://purl.org/atom/ns#";>
  <!-- This entry, however, is very necessary and also the exact
       same entry that would be PUT in the "canonical" form. -->
  <title>Some Entry</title>
  <id>http://example.com/myRecentEntry</id>
  <issued>2003-09-08T03:32:51Z</issued>
  <content type="text/plain">This is just an example.</content>
</entry>

If there is a reason why this isn't acceptable, could you document that in
the Pace?

-- Jason