Paul Sandoz (via Nabble) wrote:
> On Jan 26, 2009, at 1:44 PM, Gili wrote:
> My understanding is a 300 response is about *related representations*
> not about related resources i.e. the former is more specific than the
> latter, and i my assumption is your use-case fits into the latter
> category. Is my assumption correct?
Correct.
> > Can you please give a concrete example of when a 300 response would be
> > appropriate?
> >
>
> A request to "/content" returns distinct URLs:
>
> /content.xml
> /content.json
>
> Or returning the languages supported when the accept language header
> is not supplied.
How do 300 MULTIPLE_CHOICES and the Vary header relate to one another?
1) Can you give an example of how Vary can be used without 300
MULTIPLE_CHOICES? Or are the two always used together?
2) How can the server specify not just the names of the headers that may
be manipulated (Accept*) but also the possible values?
3) If the user hits /content but doesn't specify Accept, how can 300
MULTIPLE_CHOICES return a list of choices all having the same URL (i.e.
/content) but with different Accept headers?
Thanks,
Gili
--
View this message in context: http://n2.nabble.com/300-MULTIPLE-CHOICES-tp2209176p2220927.html
Sent from the Jersey mailing list archive at Nabble.com.