[CacheStorage] Initialize the cache backend immediately upon opening

[CacheStorage] Initialize the cache backend immediately upon opening instead of lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, like the rest of the class.

BUG=629544
Committed: https://crrev.com/7a545c04d6a45b90b1b021eff572c0a72c8f6c0a
Cr-Commit-Position: refs/heads/master@{#406430}

[jkarlin, 2016-07-19 17:11:05]

Patchset #1 (id:1) has been deleted

[jkarlin, 2016-07-19 17:15:05]

Description was changed from

==========
[WIP] [CacheStorage] Initialize the cache backend immediately upon opening

We lazily open the cache backend on the first cache operation after opening the
cache. But there can be some delay between Open completing (and the promise
resolving) and the next command. We should open the backend immediately so that
the next command doesn't have to wait for it. There is no point in opening a
cache without using it so it makes sense to not lazily init.

BUG=
==========

to

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

We lazily open the cache backend on the first cache operation after opening the
cache. But there can be some delay between Open completing (and the promise
resolving) and the next command. We should open the backend immediately so that
the next command doesn't have to wait for it. There is no point in opening a
cache without using it so it makes sense to not lazily init.

BUG=629544
==========

[jkarlin, 2016-07-19 17:50:51]

Description was changed from

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

We lazily open the cache backend on the first cache operation after opening the
cache. But there can be some delay between Open completing (and the promise
resolving) and the next command. We should open the backend immediately so that
the next command doesn't have to wait for it. There is no point in opening a
cache without using it so it makes sense to not lazily init.

BUG=629544
==========

to

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, in line with the rest of
the class.

BUG=629544
==========

[jkarlin, 2016-07-19 17:51:06]

Description was changed from

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, in line with the rest of
the class.

BUG=629544
==========

to

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, like the rest of the class.

BUG=629544
==========

[jkarlin, 2016-07-19 17:52:17]

jkarlin@chromium.org changed reviewers:
+ jsbell@chromium.org

[jkarlin, 2016-07-19 17:52:27]

jsbell@ PTAL, thanks!

[jsbell, 2016-07-19 23:03:14]

lgtm

[jkarlin, 2016-07-20 00:39:48]

The CQ bit was checked by jkarlin@chromium.org

[commit-bot: I haz the power, 2016-07-20 00:40:39]

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, 2016-07-20 00:46:07]

Description was changed from

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, like the rest of the class.

BUG=629544
==========

to

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, like the rest of the class.

BUG=629544
==========

[commit-bot: I haz the power, 2016-07-20 00:46:08]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2016-07-20 00:46:20]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-20 00:47:52]

Description was changed from

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, like the rest of the class.

BUG=629544
==========

to

==========
[CacheStorage] Initialize the cache backend immediately upon opening instead of
lazily.

Caches are used immediately after opening, we shouldn't lazily init them.

This CL:
1) Immediately initializes its backend upon creation
2) Changes the init method to use a pending closure, like the rest of the class.

BUG=629544

Committed: https://crrev.com/7a545c04d6a45b90b1b021eff572c0a72c8f6c0a
Cr-Commit-Position: refs/heads/master@{#406430}
==========

[commit-bot: I haz the power, 2016-07-20 00:47:53]

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