Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decode/Encode unaware of Selected Sub-Protocol #310

Open
dansiviter opened this issue Nov 6, 2019 · 0 comments
Open

Decode/Encode unaware of Selected Sub-Protocol #310

dansiviter opened this issue Nov 6, 2019 · 0 comments
Labels
API (Both) Impacts the client and server API enhancement Adding a new feature or improving an existing one
Milestone

Comments

@dansiviter
Copy link

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 to Decoder or Encoder. The use-case is to have subtly different encoding/decoding based on sub-protocol.

@markt-asf markt-asf added API (Both) Impacts the client and server API Jakarta EE 10 enhancement Adding a new feature or improving an existing one labels Apr 16, 2020
@markt-asf markt-asf added this to the backlog milestone May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API (Both) Impacts the client and server API enhancement Adding a new feature or improving an existing one
Projects
None yet
Development

No branches or pull requests

2 participants