The spec assumes that stream/request-format is only sent when a stream is already ongoing. But never defines how servers should behave when it's received without a stream.
As currently defined, it currently forces the server to start the stream (depending on how you interpet it):
Response: stream/start for the requested role(s) with the new format.
After receiving this message, the server responds with stream/start for the artwork role with the new format, followed by
immediate artwork updates through binary messages.
A simple solution would be to only accept stream/request-format during streams.
But I can definitely also see the benefit of requesting a format before the stream starts so the buffer doesn't get filled up before a client is allowed to select a lower quality.
The spec assumes that
stream/request-formatis only sent when a stream is already ongoing. But never defines how servers should behave when it's received without a stream.As currently defined, it currently forces the server to start the stream (depending on how you interpet it):
A simple solution would be to only accept
stream/request-formatduring streams.But I can definitely also see the benefit of requesting a format before the stream starts so the buffer doesn't get filled up before a client is allowed to select a lower quality.