- From: mike amundsen <mamund@yahoo.com>
- Date: Thu, 26 Jul 2012 06:05:47 -0400
- To: Danny Ayers <danny.ayers@gmail.com>
- Cc: W3C TAG <www-tag@w3.org>
- Message-ID: <CAPW_8m7GXvpuBuTbTGW+EFfaHbQu1iAukztm3VL5FuZAnAyeOw@mail.gmail.com>
Consider the following: Resource /q1w2e3r4 contains sales information my region. *** request GET /resource/q1w2e3r4 accept: text/csv *** response 200 OK content-type: text/csv ... north,south,east,west 100,200,300,200 *** request PUT /resource/q1w2e3r4 content-type: application/x-www-form-urlencoded ... north=100&south=200&east=350&west=150 Now what does a GET request using accept" text/csv return? mca http://amundsen.com/blog/ http://twitter.com@mamund http://mamund.com/foaf.rdf#me On Thu, Jul 26, 2012 at 5:39 AM, Danny Ayers <danny.ayers@gmail.com> wrote: > I've struggled with this myself, on seeing the same question appear on > another list I think it's worth posing. I'd appreciate clarification. > > Server-side you have a named resource. You PUT something there in a > given media type, what expectations have you over other media types? > My feeling was it doesn't matter, as long as the HTTP contract, any > subsequent GET will give something appropriate. Hopefully the change > percolates. But although that makes sense, it's kinda vague. The > interpretation I saw by this guy on a list, trying to follow the spec > properly, was like there were different buckets hanging of the > resource, you push some json, the json bucket changes. Does that > influence the other buckets? > > Might have to dig Roy up, but clarification on this would help. > > Cheers, > Danny. > > -- > http://dannyayers.com > > http://webbeep.it - text to tones and back again > >
Received on Thursday, 26 July 2012 10:06:42 UTC