Add a skeleton gamepad resource.

Add a skeleton gamepad resource.

This implements the skeleton of the gamepad resource for the IPC proxy. It is not actually hooked up. Hooking it up will require moving some gamepad lock code to a shared location.

This also hooks up the browser message routing for implementing resource hosts in the browser process.

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=153265

[raymes, 2012-08-23 15:52:32]

My guess is that you don't want to call into the in-process implementation from
the renderer side because it will be too slow?

http://codereview.chromium.org/10824272/diff/11002/content/browser/renderer_h...
File content/browser/renderer_host/pepper/pepper_gamepad_host.h (right):

http://codereview.chromium.org/10824272/diff/11002/content/browser/renderer_h...
content/browser/renderer_host/pepper/pepper_gamepad_host.h:30: BrowserPpapiHost*
browser_ppapi_host_;
Probably good to make a note about pointer ownership somewhere?

[brettw, 2012-08-23 21:22:28]

This is a synchronous API so we need to have the data in shared memory. It would
work to go through the renderer but then it would grab the shared memory from
inside the gamepad guts and duplicate it over to the plugin. It ends up being (I
think!) no less work to just talk directly to the browser.

[raymes, 2012-08-23 21:56:11]

lgtm