Re: [dxwg] Specify the realisation order of precedence for conflicting profile negotiation situations

I suggest a principle and then we have to work out the details. The principle is: the more deliberately implemented realisation should win.

So, QSA over HTTP (as QSA is a fixed thing, HTTP could be auto-set by a server).

I can’t yet decide about QSA v. REST. In the REST test I’m now doing, there are more fixed ways of specifying a profile but no option for preferences, unlike HTTP & QSA. So perhaps REST over QSA.

I will add test examples here to debate.

GitHub Notification of comment by nicholascar
Please view or discuss this issue at using your GitHub account

Received on Saturday, 27 October 2018 23:24:29 UTC