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.

Sign up for GitHub

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

Jump to bottom

Give WebSocketContainer on the client side a lifecycle #212

Open
glassfishrobot opened this issue Aug 1, 2013 · 3 comments
Open

Give WebSocketContainer on the client side a lifecycle #212

glassfishrobot opened this issue Aug 1, 2013 · 3 comments
Labels
API (Both) Impacts the client and server API enhancement Adding a new feature or improving an existing one
Milestone
2.2

Comments

@glassfishrobot
Copy link

Currently there is no way for the implementation to know when the developer has finished using each instance of the WebSocketContainer. If the developer uses ContainerProvider.getWebSocketContainer() to obtain many instances, this is difficult to manage for the implementation.

Consider adding a lifecycle so the implementation can clean up.
@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by dannycoward

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA WEBSOCKET_SPEC-212

@glassfishrobot
Copy link
Author

@glassfishrobot glassfishrobot added Priority: Major enhancement Adding a new feature or improving an existing one labels Feb 12, 2018
This was referenced Apr 23, 2018
Closed
Closed
@joakime joakime mentioned this issue Jun 12, 2018
Closed
@joakime joakime mentioned this issue Feb 18, 2019
Closed
@markt-asf markt-asf added API (Both) Impacts the client and server API Jakarta EE 10 and removed Priority: Major labels May 7, 2020
@joakime joakime mentioned this issue Apr 8, 2021
Closed
@markt-asf markt-asf added this to the 2.2 milestone May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API (Both) Impacts the client and server API enhancement Adding a new feature or improving an existing one
Projects
None yet
Milestone
2.2
Development

No branches or pull requests
2 participants
@markt-asf @glassfishrobot