Add MemoryCoordinator::SetClientMemoryState and GetClientMemoryState

Add MemoryCoordinator::SetClientMemoryState and GetClientMemoryState

This CL adds methods SetClientMemoryState and GetClientMemoryState to
MemoryCoordinator. The setter dispatch memory state change to
MemoryCoordinatorClients registerd by MemoryCoordinatorClientRegistry
in the browser process. The getter returns the current memory state
of the clients.

BUG=639700

[hajimehoshi, 2016-10-12 07:59:40]

hajimehoshi@chromium.org changed reviewers:
+ bashi@chromium.org, chrisha@chromium.org, haraken@chromium.org

[hajimehoshi, 2016-10-12 07:59:41]

PTAL

[haraken, 2016-10-12 08:11:45]

https://codereview.chromium.org/2413643002/diff/1/content/browser/memory/memo...
File content/browser/memory/memory_coordinator.cc (right):

https://codereview.chromium.org/2413643002/diff/1/content/browser/memory/memo...
content/browser/memory/memory_coordinator.cc:85: void
MemoryCoordinator::SetClientMemoryState(base::MemoryState memory_state) {

Who are you assuming calls this method?

Also Chris' proposal is to introduce MemoryCoordinatorProxy, right?

I might want to see a proof-of-concept CL that implements MCP and changes MC and
CMC using MCP. Also we need to add tests.

[hajimehoshi, 2016-10-12 08:31:55]

On 2016/10/12 08:11:45, haraken wrote:
>
https://codereview.chromium.org/2413643002/diff/1/content/browser/memory/memo...
> File content/browser/memory/memory_coordinator.cc (right):
> 
>
https://codereview.chromium.org/2413643002/diff/1/content/browser/memory/memo...
> content/browser/memory/memory_coordinator.cc:85: void
> MemoryCoordinator::SetClientMemoryState(base::MemoryState memory_state) {
> 
> Who are you assuming calls this method?
> 
> Also Chris' proposal is to introduce MemoryCoordinatorProxy, right?
> 
> I might want to see a proof-of-concept CL that implements MCP and changes MC
and
> CMC using MCP. Also we need to add tests.

As we discussed offline, we confirmed the necessity of the current memory state
management (and its getter) before creating the proxy but this is being
implemented at MemoryCoordinatorImpl. I've not noticed
https://codereview.chromium.org/2374343002/. Let me close this.

[hajimehoshi, 2016-10-12 08:32:09]

Description was changed from

==========
Add MemoryCoordinator::SetClientMemoryState and GetClientMemoryState

This CL adds methods SetClientMemoryState and GetClientMemoryState to
MemoryCoordinator. The setter dispatch memory state change to
MemoryCoordinatorClients registerd by MemoryCoordinatorClientRegistry
in the browser process. The getter returns the current memory state
of the clients.

BUG=639700
==========

to

==========
Add MemoryCoordinator::SetClientMemoryState and GetClientMemoryState

This CL adds methods SetClientMemoryState and GetClientMemoryState to
MemoryCoordinator. The setter dispatch memory state change to
MemoryCoordinatorClients registerd by MemoryCoordinatorClientRegistry
in the browser process. The getter returns the current memory state
of the clients.

BUG=639700
==========