 |
 |
On 12/2/13 10:50 AM, Robert Sanderson wrote: > On Sun, Dec 1, 2013 at 4:25 PM, Richard Wallis < > [log in to unmask]> wrote: >> As to discovering then using the (currently implemented) URI returned from >> a content-negotiated call - The standard http libraries take care of that, >> like any other http redirects (301,303, etc) plus you are protected from >> any future backend server implementation changes. > > No they don't, as there's no way to know which representations are > available via conneg, and hence no automated way to construct the Accept > header. To me this is the biggest issue with content negotiation for machine APIs. What you get may be influenced by the Accept headers you send, but without detailed knowledge of the particular system you are interacting with you can't predict what you'll actually get. Cheers, Simeon