Currently, when calling createBidirectionalStream you can specify a priority (same also for unidirectional stream):
priority {string} The priority level of the stream. One of 'high', 'default', or 'low'. Default: 'default'.
The W3C specification for webtransport defines a sendGroup mechanism; see https://www.w3.org/TR/webtransport/#sendGroup.
For me, this is not the most important mechanism (but I can not tell for others), but I just wanted to bring it to your attention (@jasnell) and ask if it is worth thinking about an implementation that aligns with this spec, as the workgroup has put much thought into it.
Currently, I think it is a very different approach.
Currently, when calling
createBidirectionalStreamyou can specify apriority(same also for unidirectional stream):The W3C specification for webtransport defines a
sendGroupmechanism; see https://www.w3.org/TR/webtransport/#sendGroup.For me, this is not the most important mechanism (but I can not tell for others), but I just wanted to bring it to your attention (@jasnell) and ask if it is worth thinking about an implementation that aligns with this spec, as the workgroup has put much thought into it.
Currently, I think it is a very different approach.