diff options
author | akalin@chromium.org <akalin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-18 04:19:16 +0000 |
---|---|---|
committer | akalin@chromium.org <akalin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-18 04:19:16 +0000 |
commit | 099bc7e6c3ef7da24f2be9d90c551cfb48a1de67 (patch) | |
tree | bed3f5b17a2a193d243913bcdf18edd6baed7cc2 /ui/aura/client/window_move_client.h | |
parent | 18b57741ac9a7be40700f906ff59267f40265c78 (diff) | |
download | chromium_src-099bc7e6c3ef7da24f2be9d90c551cfb48a1de67.zip chromium_src-099bc7e6c3ef7da24f2be9d90c551cfb48a1de67.tar.gz chromium_src-099bc7e6c3ef7da24f2be9d90c551cfb48a1de67.tar.bz2 |
[SPDY] Refactor SpdySession state machine (take 2)
Represent a SpdySession's state by three variables of type:
AvailabilityState, ReadState (the old State type), and WriteState.
Make some important functions, including the BufferedSpdyWriter
callbacks, do nothing if availability_state_ == STATE_CLOSED.
Rename the current state machine from DoLoop etc. to DoReadLoop.
Refactor the write state machine to be parallel to the read state machine.
Keep track of the number of bytes read without yielding in DoReadLoop
itself. This fixes a slight bug where the counter isn't reset if the loop
yields due to ERR_IO_PENDING being returned.
The new write state machine (DoWriteLoop, etc.) has almost the same
behavior as the old one, except if a write completes asynchronously
the write loop is immediately re-entered instead of via a posted task.
Fix tests to match new write loop behavior.
Use time_func_ consistently.
Add regression test for http://crbug.com/261043 .
BUG=255701,261043
R=rch@chromium.org, rtenneti@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=211852
Review URL: https://codereview.chromium.org/18143005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212242 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/aura/client/window_move_client.h')
0 files changed, 0 insertions, 0 deletions