Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#3518 closed enhancement (implemented)

Update circuit-launch and predictive circuit-launch logic for prop 171

Reported by: nickm Owned by: nickm
Priority: Medium Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client
Cc: Actual Points:
Parent ID: #1865 Points:
Reviewer: Sponsor:


Once we implement stream isolation correctly (#3517), we will need to revise our code that launches circuits for predicted streams and our code that launches circuits for unhandled streams.

Right now (first approximation), we launch circuits until every unhandled stream has at least one in-progress circuit that it could attach to. But prop 171 breaks that behavior, since just because in-progress circuit C could handle stream A or handle stream B, it does not follow that it could handle A and B simultaneously.

There are similar issues with predicted circuits; we should analyze them in more depth too.

Child Tickets

Change History (5)

comment:1 Changed 9 years ago by nickm

Owner: set to nickm
Status: newaccepted

comment:2 Changed 9 years ago by nickm

Status: acceptedneeds_review

I did the part about launching circuits in my prop171 branch; I am satisfied with leaving the predicted circuit code alone for now.

comment:3 Changed 9 years ago by nickm

Resolution: implemented
Status: needs_reviewclosed

comment:4 Changed 8 years ago by nickm

Keywords: tor-client added

comment:5 Changed 8 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.