Add separate ContentClient interfaces for gpu/plugin/renderer processes. Since we don't have a n...

Add separate ContentClient interfaces for gpu/plugin/renderer processes.  Since we don't have a need for a chrome/gpu or chrome/plugin directory, their chrome implementations are in chrome/common.  Use the renderer one for getting the sad plugin image.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=78617

[Avi (use Gerrit), 2011-03-17 22:03:43]

LG

seems like the content layer is learning more and more about the layers on top
of it.

[jam, 2011-03-17 22:06:02]

On Thu, Mar 17, 2011 at 3:03 PM, <avi@chromium.org> wrote:

> LG
>
> seems like the content layer is learning more and more about the layers on
> top
> of it.


the goal is for this not to happen :)  the apis added to contentclient are
stuff that the embedder can't figure out on its own.  i.e. when a crash
happens, it's too late to get the GpuInfo.  embedder needs to be called ot
know that a plugin process started, or RenderView is created etc.  they can
then add their own hooks onto these objects.


>
> http://codereview.chromium.org/6708013/
>