jakartaee / jakartaee/websocket
Introduce non-blocking WebSocketContainer.connectToServer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 78
- Forks
- 47
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 1
Description
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](https://java.net/jira/browse/TYRUS-243)
#### Affected Versions
[1.0]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the WebSocketContainer.connectToServer API described in the issue and compare it with the existing non-blocking JavaScript behavior mentioned there. Determine how the Java call should return Future and report DeploymentException and other failures through it. No implementation file or test is named; done means the handshake no longer blocks and the future's success and failure behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100