NOT12 — Clarify Handling of Priority and Timeout

The issue author describes the various ways that the Priority

and Timeout QoS properties can be influenced, and mentions that

the spec is too vague about the interactions between the various

mechanisms. Specifically, the issue author enumerates the following

problems in the spec with respect to this issue:

1) If the StructuredEvent specifies a Priority/Timeout, and the

ProxyConsumer specifies a Priority/Timeout, which one "wins"?

2) Setting Priority/Timeout on a SupplierAdmin or on the Channel

is only enabled to be inherited down to a ProxyConsumer, and not

to have any actual effect. The spec does not state this.

3) Setting Priority/Timeout on a ConsumerAdmin or ProxySupplier should

be made illegal (cause UnsupportedQoS with UNSUPPORTED_PROPERTY

error code to be raised).

4) If a StructuredEvent does not contain a Priority/Timeout, does

having this property set on the ProxyConsumer affect the contents

of the StructuredEvent, or just the way the StructuredEvent is

treated with respect to these properties.

5) In the case that a Mapping filter is associated with a

ProxySupplier, and its constraints all evaluate to FALSE for a

particular event, does the "default_value" or the value for

Priority/Timeout associated with the ProxyConsumer take precedence?

Only 2740d passed