Chromium Code Reviews| Index: media/mojo/services/mojo_decryptor.h |
| diff --git a/media/mojo/services/mojo_decryptor.h b/media/mojo/services/mojo_decryptor.h |
| index 9933658b86cd84d22e89e74eaec36ea3188a0445..33642fb05980905b282500dbc692000f3d7eb7d0 100644 |
| --- a/media/mojo/services/mojo_decryptor.h |
| +++ b/media/mojo/services/mojo_decryptor.h |
| @@ -10,6 +10,7 @@ |
| #include "media/base/decryptor.h" |
| #include "media/mojo/interfaces/decryptor.mojom.h" |
| #include "mojo/public/cpp/bindings/binding.h" |
| +#include "mojo/public/cpp/system/data_pipe.h" |
| namespace media { |
| @@ -51,8 +52,19 @@ class MojoDecryptor : public Decryptor { |
| interfaces::Decryptor::Status status, |
| interfaces::VideoFramePtr video_frame); |
| + // To pass DecoderBuffers to and from the MojoDecryptorService, 2 data pipes |
| + // are required (one each way). At initialization both pipes are created, |
| + // and then the handles are passed to the MojoDecryptorService. |
| + void CreateDataPipes(); |
| + void WriteDataIntoDataPipe(const scoped_refptr<DecoderBuffer>& buffer); |
| + void ReadDataFromDataPipe(const scoped_refptr<DecoderBuffer>& buffer); |
| + |
| interfaces::DecryptorPtr remote_decryptor_; |
| + // DataPipes for serializing the data section of DecoderBuffer into/from. |
| + mojo::ScopedDataPipeProducerHandle write_pipe_; |
| + mojo::ScopedDataPipeConsumerHandle read_pipe_; |
|
xhwang
2015/12/19 18:16:30
It's probably easier to understand if we just call
jrummell
2015/12/21 23:20:55
Done.
|
| + |
| NewKeyCB new_audio_key_cb_; |
| NewKeyCB new_video_key_cb_; |