Moving BindingManager and ChildProcessConnection to base/.

Moving BindingManager and ChildProcessConnection to base/.

Removed the last dependencies to content/ for BindingManager and the various
ChildProcessConnection classes and moved them to base/.
Most notably: 
- changed the use of LauncherThread to a thread specified on creation of 
  BaseChildProcessConnection and BindingManagerImpl .
- added a new method to BaseChildProcessConnection.ConnectionCallback that lets
  clients specify extra parameters that should be passed to the created service.

BUG=702316

[Jay Civelli, 2017-04-28 04:23:57]

The CQ bit was checked by jcivelli@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-28 04:24:44]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-28 05:40:56]

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

[commit-bot: I haz the power, 2017-04-28 05:40:57]

Dry run: This issue passed the CQ dry run.

[Jay Civelli, 2017-04-28 07:16:55]

Description was changed from

==========
Moving BindingManager and ChildProcessConnection to base/.

BUG=702316
==========

to

==========
Moving BindingManager and ChildProcessConnection to base/.

As part of that, added a new method to 
BaseChildProcessConnection.ConnectionCallback that lets clients specify extra 
parameters that should be passed to the created service.

BUG=702316
==========

[Jay Civelli, 2017-04-28 07:16:56]

jcivelli@chromium.org changed reviewers:
+ boliu@chromium.org

[Jay Civelli, 2017-04-28 07:17:18]

Patchset #1 (id:1) has been deleted

[Jay Civelli, 2017-04-28 07:17:26]

Patchset #1 (id:20001) has been deleted

[Jay Civelli, 2017-04-28 07:21:22]

Description was changed from

==========
Moving BindingManager and ChildProcessConnection to base/.

As part of that, added a new method to 
BaseChildProcessConnection.ConnectionCallback that lets clients specify extra 
parameters that should be passed to the created service.

BUG=702316
==========

to

==========
Moving BindingManager and ChildProcessConnection to base/.

Removed the last dependencies to content/ for BindingManager and the various
ChildProcessConnection classes and moved them to base/.
Most notably: 
- changed the use of LauncherThread to a thread specified on creation of 
  BaseChildProcessConnection and BindingManagerImpl .
- added a new method to BaseChildProcessConnection.ConnectionCallback that lets
  clients specify extra parameters that should be passed to the created service.

BUG=702316
==========

[Jay Civelli, 2017-04-28 07:21:31]

The CQ bit was checked by jcivelli@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-28 07:21:48]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-28 08:41:37]

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

[commit-bot: I haz the power, 2017-04-28 08:41:38]

Dry run: This issue passed the CQ dry run.

[boliu, 2017-04-28 17:07:46]

so I think Connection and Service should move at the same time? they really form
a pair?

[Jay Civelli, 2017-04-28 17:12:31]

On 2017/04/28 17:07:46, boliu wrote:
> so I think Connection and Service should move at the same time? they really
form
> a pair?

They do form a pair, but wouldn't you rather have smaller CLs than a gigantic
one?
My plan is to move the service next week.

[boliu, 2017-04-28 17:16:12]

On 2017/04/28 17:12:31, Jay Civelli wrote:
> On 2017/04/28 17:07:46, boliu wrote:
> > so I think Connection and Service should move at the same time? they really
> form
> > a pair?
> 
> They do form a pair, but wouldn't you rather have smaller CLs than a gigantic
> one?
> My plan is to move the service next week.

It's just odd.. I want to see the complete thing, ie know it's possible for the
service to be moved. Then it's ok to split into smaller parts

also.. does base need BindingManager? Isn't that kind of a content thing?

[boliu, 2017-04-28 17:16:27]

and comment on base/ part

https://codereview.chromium.org/2845243002/diff/40001/base/android/java/src/o...
File
base/android/java/src/org/chromium/base/process_launcher/BaseChildProcessConnection.java
(right):

https://codereview.chromium.org/2845243002/diff/40001/base/android/java/src/o...
base/android/java/src/org/chromium/base/process_launcher/BaseChildProcessConnection.java:298:
checkOnValidThread();
no need to repeat this :p

https://codereview.chromium.org/2845243002/diff/40001/base/android/java/src/o...
base/android/java/src/org/chromium/base/process_launcher/BaseChildProcessConnection.java:457:
if (mConnectionCallback != null) {
is this check needed? should this be an assert instead?