Whether or not the selection is clearly defined by the specification, in practice I think it will always be a case of "server decides". I don't think the equal q-values add any additional difficulty to that.
#g -- Ian Stuart wrote: > On 19/01/11 08:06, Richard Jones wrote: >> and your content negotiation header says: >> >> Accept: A; q=1.0, B; q=0.8 >> Accept-Packaging: Z; q=1.0, X; q=1.0 >> >> Which combination do you return? > I agree its not a clear-cut case..... however it also has to be said > that the content negotiation header isn't helping by declaring two > options to be of equal "value" > > I would say: > A+Z, then A+X, then B+Z, then B+X > > .... FIFO-style > > (after all, if you have a preference for order, try: > > Accept-Packaging: X; q=1.0, Z; q=1.0 > > instead) > > > Even under the concept of a combined Accept model, what do you do when > you receive > > Accept-Media-Feature: A(Z); q=1.0, A(X); q=1.0, B(Z); q=0.8, B(X); q=0.8 > > ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Sword-app-techadvisorypanel mailing list Sword-app-techadvisorypanel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sword-app-techadvisorypanel
