Chromium Code Reviews
DescriptionSimplify the QuicDispatcher::OnCanWrite logic
Before a refactoring, connections used to be able to add themselves to
QuicDispatcher::write_blocked_list_ even when they weren't
write-blocked, making it necessary to give each connection only one
attempt to write. However, this is no longer the case. Thus, the
QuicDispatcher::OnCanWrite can now simply keep going until either no
work is left or a connection gets write-blocked, and it's guaranteed
that no connection will come up twice (since if it gets added back to
write_blocked_list_, it is now blocked and the loop terminates). I've
added a longer explanatory comment and inserted a stronger check to make
sure the condition holds.
Simplify QuicDispatcher::OnCanWrite logic
Most of the changes were already in net/quic/quic_dispatcher.*. Merged
missing changes.
Merge internal change: 70043318
R=rch@chromium.org
Patch Set 1 #
Total comments: 10
Patch Set 2 : Fixed wtc's comments in Patch Set 1 #
Messages
Total messages: 6 (0 generated)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||