Oct 11, 2011 at 2:34 PM
Edited Oct 11, 2011 at 2:34 PM
Well, i´ll try that (both)! From my point of view, i would expect, that any mediatype range would be handled by the framework by going through the formatters collection and choosing which type matches first (in case of */* it would be obviously the
first formatter in the collection).
A more complex scenario: If i´d have only one formatter in the list, like "application/atom+xml" and the client wants a "application/xml"...
What would the server do?
Sending atom (which is surely valid xml)?
With which media type declaration?
"application/atom+xml" would be correct, but this is not, what the client would likely expect.
As far as i know, there is no "media type specialization/derivation/inheritance" concept defined, which would apply to this scenario.
(i´ve already started a thread weeks ago on the rest-discuss group)