OkHttp Client stream and transport are tightly coupled
Ouverte
code health
P4
- Langage dominant
- Java
- Étoiles
- 12.1k
- Forks
- 4k
- Merge moyen
- 2 j 17 h
- PR mergées (30 j)
- 37
Description
The interaction between the client stream and transport for OkHttp stream starting is tightly coupled. As brought up in #1294, we should take a look at how these two classes interact and make some clear boundaries (or possibly merge them).
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start by reading this issue alongside #1294, then trace how the OkHttp client stream and transport interact during stream startup. Done means the responsibilities have clear boundaries, or the classes are intentionally merged, with the resulting design agreed and implemented.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- backend-api-design, networking
- Type d'issue
- Refactorisation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100