diff options
author | pliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-12 12:46:37 +0000 |
---|---|---|
committer | pliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-12 12:46:37 +0000 |
commit | 4c0871855cba62292ca55b2f7467d075247c725a (patch) | |
tree | 8b96fdf32f0c50b5e9e97e438f83921a9158dac4 /tools/android/common/net.h | |
parent | a756e8791d0ef190b89a80cb71c0722270f0731d (diff) | |
download | chromium_src-4c0871855cba62292ca55b2f7467d075247c725a.zip chromium_src-4c0871855cba62292ca55b2f7467d075247c725a.tar.gz chromium_src-4c0871855cba62292ca55b2f7467d075247c725a.tar.bz2 |
Support HTTP test-server based net unit tests on Android.
This changes forwarder2 to support both test-server spawner and HTTP server
forwarding.
The main issue was that the device_forwarder was killed when instantiating a
second Forwarder (Python object).
Test server based unit tests require two device-to-host redirections, one for
the test server spawner and one for the HTTP server.
The port used by the HTTP server is allocated dynamically which means that we
can't know the full forwarding configuration before we spawn a HTTP server
(through the test server spawner).
This CL changes the forwarder to let it forward new ports while it is running
by making host_forwarder a daemon. This is similar to how ADB works.
This also means that a single host_forwarder process (daemon) can now handle
multiple devices.
BUG=146979
Review URL: https://chromiumcodereview.appspot.com/11269036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167167 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/android/common/net.h')
0 files changed, 0 insertions, 0 deletions