ircv3-specifications
ircv3-specifications copied to clipboard
Add client consideration for labeled-response (batch vs non-batch)
it's difficult to know which will be generated for a given request.
It might depend on server configuration, user modes, or in some cases, may change as a result of future extensions.
Clients may therefore prefer to handle all labeled responses as if they were a BATCH, even in the single message case, for robustness and compatibility.
That's implied by "If a response consists of more than one message, a batch MUST be used to group them into a single logical response"; but I guess it doesn't hurt to say it explicitly here.