jakartaee / jakartaee/websocket

Introduce property for setting a connection timeout to the client side API

Open
#234 3 comments 0 reactions 0 assignees View on GitHub
API (Both) enhancement
Dominant language
Java
Stars
78
Forks
47
Avg merge
1h 32m
Merged PRs (30d)
1

Description

When using the JSR356 WebSocket Client side API to connect to a server:

javax.websocket.WebSocketContainer.connectToServer(...)

there is no way to specify a connection timeout. The method connectToServer() will block until it establishes a connection (which may never happen).

Some implementations (Tyrus, Jetty) provide their own specific ways to do this, but the spec does not.
#### Affected Versions
[1.1]

Contributor guide

Open the contributing guide

Research direction

Start with the JSR356 WebSocket Client API, especially the WebSocketContainer.connectToServer(...) methods, and compare the client-side timeout approaches mentioned for Tyrus and Jetty. Done means the specification defines a way for clients to set a connection timeout and the affected API behavior is documented consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.