Turn on MojoChannel

Turn on MojoChannel

Removes --enable-mojo-channel and the MojoChannel field
trial. Turns on MojoChannel permanently.

BUG=595082
Committed: https://crrev.com/1e213694248b28e9f15be63c006009e249063808
Cr-Commit-Position: refs/heads/master@{#391029}

[Ken Rockot(use gerrit already), 2016-05-02 18:17:41]

rockot@chromium.org changed reviewers:
+ jam@chromium.org

[jam, 2016-05-02 19:09:00]

lgtm

https://codereview.chromium.org/1941003002/diff/1/content/public/common/mojo_...
File content/public/common/mojo_channel_switches.h (right):

https://codereview.chromium.org/1941003002/diff/1/content/public/common/mojo_...
content/public/common/mojo_channel_switches.h:12: CONTENT_EXPORT extern const
char kMojoChannelToken[];
(not for this cl) these really should just move to
content/public/common/content_switches

https://codereview.chromium.org/1941003002/diff/1/content/renderer/render_thr...
File content/renderer/render_thread_impl.cc (right):

https://codereview.chromium.org/1941003002/diff/1/content/renderer/render_thr...
content/renderer/render_thread_impl.cc:586: :
ChildThreadImpl(Options::Builder().UseMojoChannel(true).Build()),
when is mojo channel going to be used for all processes?

[Ken Rockot(use gerrit already), 2016-05-02 19:33:08]

https://codereview.chromium.org/1941003002/diff/1/content/public/common/mojo_...
File content/public/common/mojo_channel_switches.h (right):

https://codereview.chromium.org/1941003002/diff/1/content/public/common/mojo_...
content/public/common/mojo_channel_switches.h:12: CONTENT_EXPORT extern const
char kMojoChannelToken[];
On 2016/05/02 at 19:09:00, jam wrote:
> (not for this cl) these really should just move to
content/public/common/content_switches

noted

https://codereview.chromium.org/1941003002/diff/1/content/renderer/render_thr...
File content/renderer/render_thread_impl.cc (right):

https://codereview.chromium.org/1941003002/diff/1/content/renderer/render_thr...
content/renderer/render_thread_impl.cc:586: :
ChildThreadImpl(Options::Builder().UseMojoChannel(true).Build()),
On 2016/05/02 at 19:09:00, jam wrote:
> when is mojo channel going to be used for all processes?

Work in progress. Utility process and services processes are more challenging
because we may have to resort back to using named pipes in some cases.

[Ken Rockot(use gerrit already), 2016-05-02 19:33:10]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2016-05-02 19:33:31]

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

[commit-bot: I haz the power, 2016-05-02 19:37:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-02 19:39:34]

Description was changed from

==========
Turn on MojoChannel

Removes --enable-mojo-channel and the MojoChannel field
trial. Turns on MojoChannel permanently.

BUG=595082
==========

to

==========
Turn on MojoChannel

Removes --enable-mojo-channel and the MojoChannel field
trial. Turns on MojoChannel permanently.

BUG=595082

Committed: https://crrev.com/1e213694248b28e9f15be63c006009e249063808
Cr-Commit-Position: refs/heads/master@{#391029}
==========

[commit-bot: I haz the power, 2016-05-02 19:39:36]

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

[Ken Rockot(use gerrit already), 2016-05-03 13:30:00]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1946573002/ by rockot@chromium.org.

The reason for reverting is: Speculative revert for
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2....