Decode/Encode unaware of Selected Sub-Protocol #310
Labels
API (Both)
Impacts the client and server API
enhancement
Adding a new feature or improving an existing one
Milestone
Although the sub-protocol is negotiated with with the client, there is no way to know what that is as this is only available in
Session#getNegotiatedSubprotocol()
which is not available toDecoder
orEncoder
. The use-case is to have subtly different encoding/decoding based on sub-protocol.The text was updated successfully, but these errors were encountered: