Rather than passing initial_flow_control_window all the way down the

Rather than passing initial_flow_control_window all the way down the
call stack, put it inside QuicConfig as intended: each member of
QuicConfig has a "value to send" field, so populate this at the top
level.

rtenneti: when porting to Chromium, you should add
config.SetInitialFlowControlWindowToSend(kInitialReceiveWindowSize)

in QuicStreamFactory::CreateSession, just above line 837: *session =
  new QuicClientSession(...)

Store initial flow control window for QUIC in QuicConfig. No behavior
change intended.

Added the following unit tests to EndToEndTest.cc
+ DoNotSetResumeWriteAlarmIfConnectionFlowControlBlocked
+ NegotiateMaxOpenStreams

Merge internal change: 69079363

R=rch@chromium.org, rjshade@google.com

[Ryan Hamilton, 2014-06-13 20:21:37]

lgtm

[Robbie Shade, 2014-06-13 21:16:17]

lgtm