ppapi: PPB_VpnProvider: Define PPAPI messages

ppapi: PPB_VpnProvider: Define PPAPI messages

BUG=506490

[adrian.belgun, 2016-04-27 14:57:39]

adrian.belgun@intel.com changed reviewers:
+ bbudge@chromium.org, dcheng@chromium.org

[adrian.belgun, 2016-04-27 14:57:40]

dcheng: Please review changes in ppapi_messages.h

[dcheng, 2016-04-27 17:18:59]

What's the patch that uses them? It's impossible to review IPCs in isolation,
since part of the security review is how they're used.

[bbudge, 2016-04-27 17:30:08]

Now that you've split the IDL / boilerplate into a simpler API patch, you can do
the entire implementation as a single patch. We should land the API first to
reduce review churn on subsequent patches.

It's possible to implement in two patches, by creating the resource, but
stubbing out the API. The second patch would implement the host and the
messages. Also some tests.

Locally, you should have a branch for each change, and keep them merged to make
sure everything makes sense and works correctly as previous patches change from
review.

[adrian.belgun, 2016-04-28 08:35:26]

On 2016/04/27 17:30:08, bbudge wrote:
> Now that you've split the IDL / boilerplate into a simpler API patch, you can
do
> the entire implementation as a single patch. We should land the API first to
> reduce review churn on subsequent patches.
> 
> It's possible to implement in two patches, by creating the resource, but
> stubbing out the API. The second patch would implement the host and the
> messages. Also some tests.
> 
> Locally, you should have a branch for each change, and keep them merged to
make
> sure everything makes sense and works correctly as previous patches change
from
> review.

Merged this back into the Resource implementation. Closing this.

Patches that use changes in ppapi_messages.h.
Resource: https://codereview.chromium.org/1931513002/
Resource Host: https://codereview.chromium.org/1735473002/