Changes between Version 1 and Version 2 of Ticket #19910, comment 15


Ignore:
Timestamp:
Jan 30, 2018, 4:30:11 AM (18 months ago)
Author:
arthuredelstein
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19910, comment 15

    v1 v2  
    1313This arrangement doesn't require any modification to the browser's SOCKS implementation, but it means we don't wait for the Exit to respond with CONNECTED before asking the SOCKS client to send its first data. Basically we put the "optimism" in the proxy instead of the browser. That's nice because then (1) we will get a speedup to all ordinary SOCKS clients and (2) we're patching code controlled by Tor Project.
    1414
    15 Provided the round trip between the SOCKS client and proxy is very small compared to the round-trip through the Tor network, the performance should presumably be about the same as the existing patch in Tor Browser.
     15Provided the round trip time between the SOCKS client and proxy is very small compared to the round-trip time through the Tor network, the performance should presumably be about the same as the existing patch in Tor Browser.