Use UrlRequest in PortAllocator.

Use UrlRequest in PortAllocator.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with remoting::UrlRequest interface and so a single PortAllocator
implementation can be used in all cases.

BUG=577954
Committed: https://crrev.com/c3c43e8732254dedcbd313629f8c9eba93dff6fa
Cr-Commit-Position: refs/heads/master@{#375042}

[Sergey Ulanov, 2016-02-10 23:41:06]

Description was changed from

==========
Move URL request logic out of PortAllocator implementations.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with the new remoting::UrlRequest interface and so a single
PortAllocator implementation can be used in all cases.

The new UrlLoader will be used to fetch TURN configuration.

BUG=577954
==========

to

==========
Use UrlRequest in PortAllocator.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with remoting::UrlRequest interface and so a single PortAllocator 
implementation can be used in all cases.

BUG=577954
==========

[Sergey Ulanov, 2016-02-10 23:41:07]

sergeyu@chromium.org changed reviewers:
+ jamiewalch@chromium.org

[Sergey Ulanov, 2016-02-10 23:41:24]

Patchset #1 (id:1) has been deleted

[Sergey Ulanov, 2016-02-10 23:41:31]

Patchset #1 (id:20001) has been deleted

[Sergey Ulanov, 2016-02-10 23:41:39]

Patchset #1 (id:40001) has been deleted

[Jamie, 2016-02-11 02:22:05]

lgtm

[Sergey Ulanov, 2016-02-11 21:48:16]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2016-02-11 21:49:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1681393006/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1681393006/80001

[commit-bot: I haz the power, 2016-02-11 22:41:37]

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

[commit-bot: I haz the power, 2016-02-11 22:41:38]

Try jobs failed on following builders:
  android_chromium_gn_compile_dbg on tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_chro...)

[Sergey Ulanov, 2016-02-11 22:59:49]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2016-02-11 22:59:49]

The patchset sent to the CQ was uploaded after l-g-t-m from
jamiewalch@chromium.org
Link to the patchset: https://codereview.chromium.org/1681393006/#ps100001
(title: " ")

[commit-bot: I haz the power, 2016-02-11 23:04:27]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1681393006/100001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1681393006/100001

[commit-bot: I haz the power, 2016-02-11 23:47:10]

Description was changed from

==========
Use UrlRequest in PortAllocator.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with remoting::UrlRequest interface and so a single PortAllocator 
implementation can be used in all cases.

BUG=577954
==========

to

==========
Use UrlRequest in PortAllocator.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with remoting::UrlRequest interface and so a single PortAllocator 
implementation can be used in all cases.

BUG=577954
==========

[commit-bot: I haz the power, 2016-02-11 23:47:10]

Committed patchset #3 (id:100001)

[commit-bot: I haz the power, 2016-02-16 22:39:31]

Description was changed from

==========
Use UrlRequest in PortAllocator.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with remoting::UrlRequest interface and so a single PortAllocator 
implementation can be used in all cases.

BUG=577954
==========

to

==========
Use UrlRequest in PortAllocator.

PepperPortAllocator and ChromiumPortAllocator were different only in
how they were sending HTTP requests to allocate relay session. They were
using pp::URLLoader and net::URLFetcher respectively, but otherwise
contained largely the same logic. Now URL request logic is abstracted
with remoting::UrlRequest interface and so a single PortAllocator
implementation can be used in all cases.

BUG=577954

Committed: https://crrev.com/c3c43e8732254dedcbd313629f8c9eba93dff6fa
Cr-Commit-Position: refs/heads/master@{#375042}
==========

[commit-bot: I haz the power, 2016-02-16 22:39:32]

Patchset 3 (id:??) landed as
https://crrev.com/c3c43e8732254dedcbd313629f8c9eba93dff6fa
Cr-Commit-Position: refs/heads/master@{#375042}