Tiebraking in accept specializer

[scymtym]

I would like to resolve the tiebraker TODO as follows:

• If the same media type entry is the best match for two specializers (e.g. request only has text/* and there are specializers text/plain and text/html), use string< on the specializers' media type strings.
• If two media types in the accept specification, that do not have a ancestor-descendent relation in the accept-tree, have the same q value, treat the media type that occurs earlier in the specification as preferred.

I have implemented this and could push if the approach sounds reasonable.

[csrhodes]

Jan Moringen notifications@github.com writes:

I would like to resolve the tiebraker TODO as follows:

• If the same media type entry is the best match for two specializers (e.g. request only has text/* and there are specializers text/plainandtext/html), usestring<` on the specializers' media type strings.
• If two media types in the accept specification, that do not have a ancestor-descendent relation in the accept-tree, have the same q value, treat the media type that occurs earlier in the specification as preferred.

I have implemented this and could push if the approach sounds reasonable.

That's fine. I think for full industrial-grade productization, this could turn into a tiebreaker function per generic function, but this as a default strategy (and unparameterized for now) is absolutely fine.

Cheers,

Christophe