Mojo's network service should use a disk cache on Android

Mojo's network service should use a disk cache on Android

Launching Mojo apps on Android is slow because we keep the network cache in
memory, which means we lose it every time we launch MojoShell. After this CL,
we use a disk cache on Android. Note: We still use a memory cache on desktop
because we want to be able to run many instances of mojo_shell in parallel on
desktop for testing.

R=jamesr@chromium.org
BUG=452226
Committed: https://crrev.com/d1cc658f889a6aeefed69ac49e56448c27e1df50
Cr-Commit-Position: refs/heads/master@{#313642}

[jamesr, 2015-01-28 19:30:57]

We don't run tests in parallel on android?

[abarth-chromium, 2015-01-28 20:54:13]

On 2015/01/28 at 19:30:57, jamesr wrote:
> We don't run tests in parallel on android?

Nope.  Android doesn't let you run more than one instance of a given APK.

[jamesr, 2015-01-28 23:44:41]

lgtm

[abarth-chromium, 2015-01-28 23:55:59]

lgtm

[jamesr, 2015-01-28 23:57:26]

On 2015/01/28 23:55:59, abarth wrote:
> lgtm

NO U

[abarth-chromium, 2015-01-29 00:41:39]

The CQ bit was checked by abarth@chromium.org

[abarth-chromium, 2015-01-29 00:41:56]

On 2015/01/28 at 23:57:26, jamesr wrote:
> On 2015/01/28 23:55:59, abarth wrote:
> > lgtm
> 
> NO U

Sorry.  I meant to presses the commit button.

[commit-bot: I haz the power, 2015-01-29 00:42:25]

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

[commit-bot: I haz the power, 2015-01-29 00:45:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-29 00:46:49]

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