You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extend the metered::* types to have send::<Priority = Standard> generic argument which can either be Droppable, Low, Standard, High (not an enum!, all marker types).
Pros:
allow a more nuanced handling of messages
keep the semantics simple
Cons:
Complexity:
Will require more logic around sending
Requires multiple channels per subsystem
The text was updated successfully, but these errors were encountered:
We actually don't need Droppable/Low priorities as we have try_send method. So I would propose to implement just High priority channel and configure it per-subsystem consumer. In this case we will allow each consumer to define if it should have any high priority messages or not (and the size of that priority queue as well).
Quoting from Polkadot issue paritytech/polkadot-sdk#824:
Extend the
metered::*
types to havesend::<Priority = Standard>
generic argument which can either beDroppable
,Low
,Standard
,High
(not anenum
!, all marker types).Pros:
Cons:
The text was updated successfully, but these errors were encountered: