envoyproxy/envoy

StreamInfo: split between downstream and upstream

Open

#17,594 opened on Aug 4, 2021

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)C++ (5,373 forks)batch import
help wantedtech debt

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently StreamInfo is a grab bag for fields that might not make sense for both upstream and downstream (and for that matter for all the places it is used HTTP streams, TCP connections, etc).

Consider splitting in a way that would reduce scope of the interface and make it easier to understand what a particular StreamInfo object is describing.

Contributor guide

Research direction
Analyze the StreamInfo interface and separate upstream/downstream concerns.
Tech stack
cpp
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20