Hmm, didn't think about that. I guess you will need to have some kind of request body anyways. Do you think that the request method should be set in the data though, or should it be set in the header, since the method/header defines how the data should be interpreted? I know that's just splitting hairs, but there was some concern about keeping the api as clean as possible.
-Jared On Thu, May 14, 2009 at 6:55 AM, Brian Candler <b.cand...@pobox.com> wrote: > On Thu, May 14, 2009 at 06:45:28AM -0500, Jared Scheel wrote: >> That's a great point, DELETE does often get ignored. I like the idea >> of having a reserved property in json, but it still relies on your >> ability to push json to couchdb. > > So, you want to be able to replace a PUT with a POST, in some part of the > API where the body is neither JSON nor a HTML FORM upload. > > The only example I can think of is using PUT to upload an attachment, and I > thought there was already a POST multipart/form-data alternative for that. > > What else have I forgotten? >
