jakartaee / jakartaee/websocket
Add the ability to define global encoders and decoders
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 78
- Forks
- 47
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 1
Description
In a future version of the WebSocket API, I would love to see the ability to specify global encoders and decoders both of the client and server side. This could be very similar to how you can specify JAX-RS 2 providers today (e.g. to globally handle JSON encoding/decoding with a generic tool).
Do let me know if anything needs to be explained further - I am happy to help.
Please note that these are purely my personal views and certainly not of Oracle's as a company.
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
The issue names no files, tests, or entry points. Start by reviewing the existing WebSocket API and the JAX-RS 2 provider model it references, then clarify how global encoder and decoder registration should work for both clients and servers. Done requires an agreed design and corresponding coverage for the proposed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100