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

Introduce non-blocking WebSocketContainer.connectToServer #214

Open
glassfishrobot opened this issue Aug 28, 2013 · 4 comments
Open

Introduce non-blocking WebSocketContainer.connectToServer #214

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

Comments

@glassfishrobot
Copy link

WebSocketConatiner.connectToServer currently blocks until handshake response is received, which is not very usable in some cases, like applications with UI etc. connectToServer paralell in java scipt already is non-blocking and seems like it is working very well and users might expect similar behaviour from WebSocket client.

I could see something similar to what is already present, but it would need to return Future and report DeploymentException (and others) via this returned future.

Based on user submission, see https://java.net/jira/browse/TYRUS-243

Affected Versions

[1.0]
@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by pavelbucek

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Issue-Links:
is duplicated by
WEBSOCKET_SPEC-227

@glassfishrobot
Copy link
Author

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

@glassfishrobot
Copy link
Author

@glassfishrobot glassfishrobot added Priority: Major enhancement Adding a new feature or improving an existing one labels Feb 12, 2018
@markt-asf markt-asf added API (Both) Impacts the client and server API Jakarta EE 10 and removed Priority: Major labels May 7, 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
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
backlog
Development

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