Skip to content

Ordering of messages scheduled at the exact same time #212

Closed
@djipco

Description

@djipco

It might be a good idea to specify the order in which messages scheduled for the exact same timestamp are sent.

I stumbled into a situation with JazzSoft's implementation of requestMidiAccess where control change messages intended to select an NRPN parameter are sent out of order.

This is what I am doing:

send([ 176, 99, 12 ], 5000);
send([ 176, 98, 34 ], 5000);

But the message are (sometimes) received in this order:

[ 176, 98, 34 ]
[ 176, 99, 12 ]

I believe messages scheduled for the exact same timestamp should be sent in the order they were originally queued. The spec should probably explicitly mention that.

Does that make sense?

Metadata

Metadata

Labels

Needs Editshttps://speced.github.io/spec-maintenance/about/Priority: Soonhttps://speced.github.io/spec-maintenance/about/category: enhancementhttps://www.w3.org/policies/process/#class-3

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions