Revert of Rate limit programmatic update checks for extensions

Revert of Rate limit programmatic update checks for extensions (patchset #7 id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
>
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
>
> BUG=599310
TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310, 605017
Committed: https://crrev.com/f420bc5e1085bf754adfa8fb15ab755866e03227
Cr-Commit-Position: refs/heads/master@{#388444}

[msramek, 2016-04-20 08:18:22]

Created Revert of Rate limit programmatic update checks for extensions

[msramek, 2016-04-20 08:18:38]

Description was changed from

==========
Revert of Rate limit programmatic update checks for extensions (patchset #7
id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in
the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
> 
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
> 
> BUG=599310

TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310
==========

to

==========
Revert of Rate limit programmatic update checks for extensions (patchset #7
id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in
the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
> 
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
> 
> BUG=599310

TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310,605017
==========

[msramek, 2016-04-20 08:18:52]

The CQ bit was checked by msramek@chromium.org

[commit-bot: I haz the power, 2016-04-20 08:19:07]

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

[commit-bot: I haz the power, 2016-04-20 08:19:45]

Description was changed from

==========
Revert of Rate limit programmatic update checks for extensions (patchset #7
id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in
the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
> 
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
> 
> BUG=599310

TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310,605017
==========

to

==========
Revert of Rate limit programmatic update checks for extensions (patchset #7
id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in
the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
> 
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
> 
> BUG=599310

TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310,605017
==========

[commit-bot: I haz the power, 2016-04-20 08:19:46]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-22 19:21:35]

Description was changed from

==========
Revert of Rate limit programmatic update checks for extensions (patchset #7
id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in
the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
> 
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
> 
> BUG=599310

TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310,605017
==========

to

==========
Revert of Rate limit programmatic update checks for extensions (patchset #7
id:120001 of https://codereview.chromium.org/1887253002/ )

Reason for revert:
This CL is suspected by sheriff-o-matic to have caused the perf regression in
the number of static initializers.

See crbug.com/605017 for more details.

Original issue's description:
> Rate limit programmatic update checks for extensions
>
> Previously extensions could call the runtime.requestUpdateCheck method
> as often as every 5 seconds. This CL introduces a more restrictive
> policy of around one extra check per autoupdate period, and changes the
> implementation location of the rate limiting from within the
> ExtensionUpdater code itself to the ChromeRuntimeAPIDelegate, and makes
> it more flexible by using net::BackoffEntry.
>
> BUG=599310

TBR=rdevlin.cronin@chromium.org,asargent@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=599310,605017

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

[commit-bot: I haz the power, 2016-04-22 19:21:36]

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