[NOT FOR REVIEW][PPAPI] Implement MediaStreamVideoTrack pepper API

Implement MediaStreamVideoTrack pepper API

MediaStreamTrack Classes Hierarchy
https://docs.google.com/a/google.com/document/d/19bkcUW8WGvXhNHEaDYxnq8JH9LCWsB4a8kxJyPEJzTc/edit#heading=h.ytqwc0tznx3k

BUG=330851

[Peng, 2014-01-07 20:08:14]

Hi,

During reviewing of CL 119853003, I found a circular buffer is not a good idea
for MediaStream API. It can not support accessing multi-frames at same time. So
I re-implemented the VideoTrack CL to use a shared memory directly. Sorry for
wasting your time on the old CL.

PTAL. Thanks.

[yzshen1, 2014-01-07 23:57:35]

Hi, Peng:

A few high level comments:
- Please consider splitting the code into multiple CLs, for example:
  * the API boilerplates: *_api, *_thunk and many other files except the real
implementation
  * the real implementation: *_host, *_resource
  * the example.

  That is actually a faster way to get your code landed. It reduces the work of
resolving conflicts. It avoids the risk of all code being reverted if any issues
show up on the waterfall. Besides, some less critial code such as example won't
block the other part. And it is easiers for reviewers to do load balancing.

  (I am not saying that it is a must. If you still feel like to go ahead with a
single big CL, that is fine. But please think about it. :))

- Maybe we don't need to make MediaStreamTrackBaseShared a base class. You could
call it MediaStreamFrameBuffer and make it a member of Track classes.

What do you think?

https://codereview.chromium.org/101463008/diff/120002/ppapi/thunk/interfaces_...
File ppapi/thunk/interfaces_ppb_public_stable.h (right):

https://codereview.chromium.org/101463008/diff/120002/ppapi/thunk/interfaces_...
ppapi/thunk/interfaces_ppb_public_stable.h:70:
PROXIED_IFACE(PPB_MEDIASTREAMVIDEOTRACK_INTERFACE_0_1,
Please put them in interfaces_ppb_public_dev_channel.h

[Peng, 2014-01-08 15:07:11]

On 2014/01/07 23:57:35, yzshen1 wrote:
> Hi, Peng:
> 
> A few high level comments:
> - Please consider splitting the code into multiple CLs, for example:
>   * the API boilerplates: *_api, *_thunk and many other files except the real
> implementation
>   * the real implementation: *_host, *_resource
>   * the example.
> 
>   That is actually a faster way to get your code landed. It reduces the work
of
> resolving conflicts. It avoids the risk of all code being reverted if any
issues
> show up on the waterfall. Besides, some less critial code such as example
won't
> block the other part. And it is easiers for reviewers to do load balancing.
> 
>   (I am not saying that it is a must. If you still feel like to go ahead with
a
> single big CL, that is fine. But please think about it. :))
> 
> - Maybe we don't need to make MediaStreamTrackBaseShared a base class. You
could
> call it MediaStreamFrameBuffer and make it a member of Track classes.
> 
> What do you think?

That is really good idea. I will split this CL to several small CLs. Thanks

> 
>
https://codereview.chromium.org/101463008/diff/120002/ppapi/thunk/interfaces_...
> File ppapi/thunk/interfaces_ppb_public_stable.h (right):
> 
>
https://codereview.chromium.org/101463008/diff/120002/ppapi/thunk/interfaces_...
> ppapi/thunk/interfaces_ppb_public_stable.h:70:
> PROXIED_IFACE(PPB_MEDIASTREAMVIDEOTRACK_INTERFACE_0_1,
> Please put them in interfaces_ppb_public_dev_channel.h