Land Recent QUIC Changes.

Land Recent QUIC Changes.

Removing deprecated flag FLAGS_enable_quic_stream_flow_control_2
Per-stream flow control is deemed safe at this point (the bug is open
due to connection level flow control) so we can kill it off as a part of
removing Qv17.

removing deprecated flag FLAGS_enable_quic_stream_flow_control_2

Merge internal change: 69784569
https://codereview.chromium.org/346303006/


Added ProcessPacketInterface interface and QuicDispatcher is derived
from it.

This change is the merge of "QUIC backend group code for UDP proxy
session" CL.

Merge internal change: 69778759
https://codereview.chromium.org/352253002/


Changes congestion-options used in the config to a more general
connection-options.

Merge internal change: 69773863
https://codereview.chromium.org/353903003/


Documented HandshakeFailureReason's enum values with one-sentence
comments.

Minor change to keep the code similar to chromium.

Merge internal change: 69773346
https://codereview.chromium.org/359483002/


Allow QUIC pacing and time-based loss detection to be enabled via
congestion options.

Merge internal change: 69683639
https://codereview.chromium.org/354523004/

R=rch@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=280166

[ramant (doing other things), 2014-06-26 03:25:27]

Hi Ryan,
  Wanted to merge all crypto related changes (and other changes that come after
it) and land them in a separate CL. Thus created this CL until merging of CL
that changes crypto code. Sorry for extra landing of CLs.

thanks
raman

[Ryan Hamilton, 2014-06-26 15:47:11]

lgtm

Your plan of doing the other changes in a different CL makes sense.

[ramant (doing other things), 2014-06-26 17:26:15]

The CQ bit was checked by rtenneti@chromium.org

[commit-bot: I haz the power, 2014-06-26 17:27:41]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rtenneti@chromium.org/357573004/1

[commit-bot: I haz the power, 2014-06-26 17:44:36]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/8...)
  android_chromium_gn_compile_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_chromium_gn_c...)
  android_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_clang_dbg/bui...)
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/20...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_clang_...)
  linux_chromium_gn_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_gn_rel...)
  linux_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel/bu...)
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)
  win_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_compile_...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/22028)
  win_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu/builds/26332)

[commit-bot: I haz the power, 2014-06-26 17:48:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-06-26 17:48:19]

Try jobs failed on following builders:
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/22037)

[ramant (doing other things), 2014-06-26 18:12:51]

The CQ bit was checked by rtenneti@chromium.org

[commit-bot: I haz the power, 2014-06-26 18:17:15]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rtenneti@chromium.org/357573004/40001

[commit-bot: I haz the power, 2014-06-26 23:40:35]

Change committed as 280166

[wtc, 2014-06-30 23:33:35]

Patch set 2 LGTM.