-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Removing moved Extension classes from jetty-websocket-api #3453
Comments
Most of the extension behaviors have been moved to To document for future viewers of this issue ...
|
joakime
added a commit
that referenced
this issue
Mar 12, 2019
…t-api Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Mar 12, 2019
…t-api Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Opened PR #3455 |
joakime
changed the title
user supplied extensions are not implemented through the jetty-websocket-api in jetty 10.0.x
Removing moved Extension classes from jetty-websocket-api
Mar 12, 2019
gregw
added a commit
that referenced
this issue
Mar 13, 2019
…ated-websocket-extension-api Issue #3453 - Removing deprecated Extension classes in jetty-websocket-api
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
classes defining jetty-api extensions exist such as
but these don't seem to be used or tested anywhere
The text was updated successfully, but these errors were encountered: