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

Need a way to configure WebSocketContainer #205

Closed
glassfishrobot opened this issue May 30, 2013 · 5 comments
Closed

Need a way to configure WebSocketContainer #205

glassfishrobot opened this issue May 30, 2013 · 5 comments
Labels
API (Both) Impacts the client and server API duplicate This issue or pull request already exists wontfix This will not be worked on

Comments

@glassfishrobot
Copy link

Need a way to configure the WebSocketContainer (for e.g thread pool, say security configuration etc). This way one can customize the container with a standard configuration or can extend it using a provider specific configuration.

Suggesting a new method
ContainerProvider#getWebSocketContainer(Map<String, ?> config)

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by jitu

@glassfishrobot
Copy link
Author

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

@glassfishrobot
Copy link
Author

@markt-asf markt-asf added API (Both) Impacts the client and server API duplicate This issue or pull request already exists wontfix This will not be worked on and removed Priority: Major Type: Improvement labels May 7, 2020
@markt-asf
Copy link
Contributor

This very quickly gets into implementation specifics. Generally, implementations seem to be using the userProperties of the provided ClientEndpointConfig to provide implementation specific configuration. There is a separate issue (#210) to provide an SSLContext. That is common enough to all implementations that I expect it will be added to the API.

@jansupol
Copy link
Contributor

jansupol commented May 8, 2020

Assumingly there would need to be a way to cooperate with Microprofile Config once it's adopted by Jakarta. The information in the config file could be vendor specific, the config to me makes sense to be passed directly to the API, though.

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 duplicate This issue or pull request already exists wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants