Add a private PPB_Talk_Private interface.

Add a private PPB_Talk_Private interface.

It exposes one function that sends a message to the browser and issues a reply. The browser doesn't implement this yet.

BUG=117564
TEST=

[brettw, 2012-03-09 21:13:11]

This was more files that I would have liked, oh well.

You would hook up handling this message to the
content/browser/renderer_host/pepper_message_filter.h

[Josh Horwich, 2012-03-09 21:59:33]

This is great! Thank you for the quick turnaround.

I'll try using this locally (w/ fix for compile breakage) ahead of this patch
landing.

https://chromiumcodereview.appspot.com/9666020/diff/1/ppapi/proxy/ppapi_messa...
File ppapi/proxy/ppapi_messages.h (right):

https://chromiumcodereview.appspot.com/9666020/diff/1/ppapi/proxy/ppapi_messa...
ppapi/proxy/ppapi_messages.h:302: int32_t /* result */);
Looks like the semicolon is breaking builds, e.g. linux_rel:

  CXX(target)
out/Release/obj.target/test_shell_tests/webkit/plugins/ppapi/url_request_info_unittest.o
In file included from ./chrome/common/all_messages.h:20,
                 from chrome/tools/ipclist/ipclist.cc:31:
./ppapi/proxy/ppapi_messages.h:303: error: expected primary-expression before
';' token

[varunjain, 2012-03-09 23:36:31]

https://chromiumcodereview.appspot.com/9666020/diff/4001/ppapi/thunk/ppb_talk...
File ppapi/thunk/ppb_talk_private_thunk.cc (right):

https://chromiumcodereview.appspot.com/9666020/diff/4001/ppapi/thunk/ppb_talk...
ppapi/thunk/ppb_talk_private_thunk.cc:37: const PPB_Talk_Private_1_0*
GetPPB_Talk_Private_1_0_Thunk() {
needs a PPAPI_THUNK_EXPORT

[brettw, 2012-03-12 04:42:19]

I think I fixed the export issue (a slightly different way).

I thought about this and I think you need a message associated with a page. The
way I implemented the browser messages in this patch is that the message will
arrive on the I/O thread of the browser without any context, and you won't know
which tab to display an infobar for.

If we go though the renderer we can write a ViewHostMsg_ which will arrive on
the UI thread associated with the tab.

[brettw, 2012-03-12 23:29:44]

Unfortunately, I don't have time to work on this now, and I realistically won't
have any time to program at all until Thursaday at the earliest.

So this is a non-compiling patch that hopefully has the skeleton pieces in
place. Here is how everything should work:


Create call:
  - Calls interface in _proxy.cc. This sends sync create message to renderer
    (see other resources' create messages).
  - Message received by Proxy object. This makes call in browser.
  - Do not use ResourceCreationProxy, get the C interface directly via
    local_get_interface(PPB_TALK_PRIVATE_INTERFACE_1_0).
  - This should call into the implementation of the interface in chrome/renderer

GetPermissionCall:
  - Calls interface in _proxy.cc, sends async message to renderer
  - Message received by proxy object in PPB_Talk_Private_Proxy, calls through
    to object implemented in chrome/renderer.
  - chrome/renderer/chrome/ppb_talk_...cc sends routed message to browser,
  - Add a filter for this message in
chrome/browser/renderer_host/chrome_render_view_host_observer.h
  - Send back ACK message containing host_resource and result int32
  - Talk_Impl object registered itself as a filter for the RenderView in its
    constructor. It checks for this message.
  - When it gets the reply, it ussues the callback.
  - This should call OnGotPermission in the proxy (I sketched this out) which
    was set as the completion callback
  - This sends a message back to the plugin
  - Received in the PPB_Talk_Private_Proxy::OnMsgGetPermissionACK and forwards
    it to the object.