Request for Comment! Priority Matching - semantic breaking change

[Daniel Worthington-Bodart]

Hey people,

I'd like to make a semantic change to MatchQuality

Currently the Priority attribute can be used to override which resource is chosen when there is a tie break however it can be trumped by client negotiation (Accept Header Quality (q) flag) or number of path segments.

I feel that the attribute should definitely override client quality level and am wondering it it should just trump everything for good measure. This will mean the ultimately the developer can override any tie.

Unless anyone objects I'm going to make this change in the next day or 2. 

This will be a semantic breaking change so it's important that you speak up if have concerns

Thanks 

Dan

[Matt Savage]

Nothing to add in terms of impact of apps I look after (because I'm not working on any UI apps right now), but this is definitely the least surprising behaviour to my brain.

--
You received this message because you are subscribed to the Google Groups "utterlyidle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to utterlyidle...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.