Use getDataBufferingPolicy() instead of the redundant dataBufferingPolicy().

Use getDataBufferingPolicy() instead of the redundant dataBufferingPolicy().

Before this CL, blink::Resource class would define 2 almost identical methods:
- Same const-ness
- Same return type
- Same body
- Different name and access:
  public |getDataBufferingPolicy| and protected |dataBufferingPolicy|.

This CL removes the redundant dataBufferingPolicy() and tweaks the only
caller of the removed method to call getDataBufferingPolicy() instead.

This CL helps with rewrite_to_chrome_style which would have renamed
dataBufferingPolicy to getDataBufferingPolicy to avoid type-vs-method
name conflict (see r414550 and r417471).  Such rename would mean two
definitions of the same method and so would mean a build error.

BUG=582312
Committed: https://crrev.com/9fe321541270204571bfdbd4c14995046bc3986e
Cr-Commit-Position: refs/heads/master@{#437625}

[Łukasz Anforowicz, 2016-12-09 18:01:12]

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

[commit-bot: I haz the power, 2016-12-09 18:01:52]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Łukasz Anforowicz, 2016-12-09 18:02:23]

lukasza@chromium.org changed reviewers:
+ dcheng@chromium.org

[Łukasz Anforowicz, 2016-12-09 18:02:23]

Daniel, can you take a look please?

[dcheng, 2016-12-09 18:20:34]

lgtm

[Łukasz Anforowicz, 2016-12-09 18:21:27]

The CQ bit was unchecked by lukasza@chromium.org

[Łukasz Anforowicz, 2016-12-09 18:21:30]

The CQ bit was checked by lukasza@chromium.org

[commit-bot: I haz the power, 2016-12-09 18:22:15]

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-12-09 20:30:26]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481307690005640, "parent_rev":
"ee2b60d1163a37b14717c720f3245c10c31871c9", "commit_rev":
"3c180d0772ff74193ea0f49b792b33d3030e7a3d"}

[commit-bot: I haz the power, 2016-12-09 20:30:54]

Description was changed from

==========
Use getDataBufferingPolicy() instead of the redundant dataBufferingPolicy().

Before this CL, blink::Resource class would define 2 almost identical methods:
- Same const-ness
- Same return type
- Same body
- Different name and access:
  public |getDataBufferingPolicy| and protected |dataBufferingPolicy|.

This CL removes the redundant dataBufferingPolicy() and tweaks the only
caller of the removed method to call getDataBufferingPolicy() instead.

This CL helps with rewrite_to_chrome_style which would have renamed
dataBufferingPolicy to getDataBufferingPolicy to avoid type-vs-method
name conflict (see r414550 and r417471).  Such rename would mean two
definitions of the same method and so would mean a build error.

BUG=582312
==========

to

==========
Use getDataBufferingPolicy() instead of the redundant dataBufferingPolicy().

Before this CL, blink::Resource class would define 2 almost identical methods:
- Same const-ness
- Same return type
- Same body
- Different name and access:
  public |getDataBufferingPolicy| and protected |dataBufferingPolicy|.

This CL removes the redundant dataBufferingPolicy() and tweaks the only
caller of the removed method to call getDataBufferingPolicy() instead.

This CL helps with rewrite_to_chrome_style which would have renamed
dataBufferingPolicy to getDataBufferingPolicy to avoid type-vs-method
name conflict (see r414550 and r417471).  Such rename would mean two
definitions of the same method and so would mean a build error.

BUG=582312

Review-Url: https://codereview.chromium.org/2561403003
==========

[commit-bot: I haz the power, 2016-12-09 20:30:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-12 14:37:24]

Description was changed from

==========
Use getDataBufferingPolicy() instead of the redundant dataBufferingPolicy().

Before this CL, blink::Resource class would define 2 almost identical methods:
- Same const-ness
- Same return type
- Same body
- Different name and access:
  public |getDataBufferingPolicy| and protected |dataBufferingPolicy|.

This CL removes the redundant dataBufferingPolicy() and tweaks the only
caller of the removed method to call getDataBufferingPolicy() instead.

This CL helps with rewrite_to_chrome_style which would have renamed
dataBufferingPolicy to getDataBufferingPolicy to avoid type-vs-method
name conflict (see r414550 and r417471).  Such rename would mean two
definitions of the same method and so would mean a build error.

BUG=582312

Review-Url: https://codereview.chromium.org/2561403003
==========

to

==========
Use getDataBufferingPolicy() instead of the redundant dataBufferingPolicy().

Before this CL, blink::Resource class would define 2 almost identical methods:
- Same const-ness
- Same return type
- Same body
- Different name and access:
  public |getDataBufferingPolicy| and protected |dataBufferingPolicy|.

This CL removes the redundant dataBufferingPolicy() and tweaks the only
caller of the removed method to call getDataBufferingPolicy() instead.

This CL helps with rewrite_to_chrome_style which would have renamed
dataBufferingPolicy to getDataBufferingPolicy to avoid type-vs-method
name conflict (see r414550 and r417471).  Such rename would mean two
definitions of the same method and so would mean a build error.

BUG=582312

Committed: https://crrev.com/9fe321541270204571bfdbd4c14995046bc3986e
Cr-Commit-Position: refs/heads/master@{#437625}
==========

[commit-bot: I haz the power, 2016-12-12 14:37:25]

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