Subscription Priorities

[patstevens4]

Is there an existing proposal for this?

• I have searched the existing proposals

Is your feature request related to a problem?

High priority messages intermixed with low priority messages taking a while to receive on low throughput connections.

Describe the solution you'd like

I would like to specify the order in which subscriptions process incoming messages, such that high priority subscriptions always run when matching messages are available, and lower priority subscriptions fire when the higher priority subscriptions are drained for a given consumer.

It would be even better is subscription priorities could be set globally, to handle the case where critical messages are spread amongst several queues.

Alternatives you considered

1. Aggressively start and stop subscriptions for lower priority content when high priority content is available. This can be problematic with valid, low priority messages getting auto confirmed for the app and lost.