eclipse-ee4j / eclipse-ee4j/tyrus
Reuse TaskProcessor from Grizzly containers in JDK container
Open
Component: client
Priority: Trivial
Type: Improvement
- Dominant language
- Java
- Stars
- 128
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
TaskProcesssor used in both Grizzly server and client container uses the same logic as TaskQueueFilter in JDK client
#### Affected Versions
[1.6]
Contributor guide
Research direction
Start by comparing TaskProcessor in the Grizzly server and client containers with TaskQueueFilter in the JDK client, as described in the issue. Trace where each is used and determine how the shared logic could be reused in the JDK container; done means the JDK container uses the appropriate shared processing behavior without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100