Loading ...
Sorry, an error occurred while loading the content.

10609RE: [rest-discuss] Content negotiation unRESTful?

Expand Messages
  • Sebastien Lambla
    Apr 7, 2008
    • 0 Attachment
      303 and httpRange-14 is a benefit.

      -----Original Message-----
      From: rest-discuss@yahoogroups.com [mailto:rest-discuss@yahoogroups.com] On
      Behalf Of Subbu Allamaraju
      Sent: 31 March 2008 16:07
      To: Jan Algermissen
      Cc: Stefan Tilkov; REST Discuss
      Subject: Re: [rest-discuss] Content negotiation unRESTful?

      Strictly speaking, this is still agent-driven content-negotiation, and
      the redirect you are proposing may be an implementation detail. IMO,
      this redirect is not necessary. There is no need for each
      representation to get its own URI, and in some cases, it could create
      unnecessary proliferation without extra benefits.


      On Mar 31, 2008, at 7:06 AM, Jan Algermissen wrote:
      > After taking a glance at it: I am not sure about the way he quotes
      > Roy or XML vs JSON being mechanical etc. but I think it is generally
      > correct not to deliver different media types through the same
      > resource. If you have several, then publish a single URI that
      > redirects to media type specific ones based upon the Accept header.
      > That way every resource gets its own URI which gives the client more
      > control/possibilities.


      Yahoo! Groups Links
    • Show all 20 messages in this topic