The client sends the list of allowed content types in the 'Allow' http header
and the response will contain a 'Content-Type' header. This function will
try to find the best matching @SerializationResult UDA based on the allowed
content types.
Note:
Comment 1: if the request doesn't specify any allowed content types, then * / *
is assumed
Comment 2: if there are no UDA's matching the client's allowed content types, -1
is returned
Comment 3: if there are more than 1 matching UDA, for ONE specific client's allowed
content type(and their priority is the same - see below),
then the one specified earlier in the code gets chosen
The client sends the list of allowed content types in the 'Allow' http header and the response will contain a 'Content-Type' header. This function will try to find the best matching @SerializationResult UDA based on the allowed content types.
Note:
Comment 1: if the request doesn't specify any allowed content types, then * / * is assumed
Comment 2: if there are no UDA's matching the client's allowed content types, -1 is returned
Comment 3: if there are more than 1 matching UDA, for ONE specific client's allowed content type(and their priority is the same - see below), then the one specified earlier in the code gets chosen
Comment 4: accept-params(quality factor) and accept-extensions are ignored https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Comment 5: matching the most specific content type without any wildcard has priority
Comment 6: the request's content type can be in the format of