Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #5392

Closed (moved)
Open
Opened Mar 14, 2012 by Roger Dingledine@arma

Write proposal for n23 patch behavior

In #4488 (moved) we located and updated the n23 patch from the Defenestrator paper. It's now in branch 'n23-2' in my git repo.

The next step is to refactor connection_or_consider_sending_flowcontrol_cell(). To do that, we need to know what the function is supposed to be doing.

Under what circumstances do we send a flowcontrol cell, and how do we pick the values for it? Just as important, in what cases (e.g. if we're a client) do we not send flowcontrol cells?

I'm hoping Mashael will do this, with Ian's help.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#5392