Implement screen capturer for MediaStream API.

content/browser/renderer_host/media/DEPS

Index: content/browser/renderer_host/media/DEPS
diff --git a/content/browser/renderer_host/media/DEPS b/content/browser/renderer_host/media/DEPS
index c3a5b96fc44d4dabd31a53ec0db441642bc2ceeb..fbe765775c174b99ffdb7ef5ee5aff7cde58691d 100644
--- a/content/browser/renderer_host/media/DEPS
+++ b/content/browser/renderer_host/media/DEPS
@@ -1,3 +1,4 @@
 include_rules = [
   "+media",
+  "+remoting/capturer",

[jam, 2013/01/18 02:58:35]

remoting is a chrome feature, i.e. it's not part of the web platform. why does
content have to know about this?

if there's common code in remoting directory that'll be used for webrtc (?),
then it should be moved out of remoting..

[Sergey Ulanov, 2013/01/18 18:39:04]

remoting/capturer is a separate library that implements screen capturing and it
doesn't depend on any other parts of remoting code. Here I'm reusing it to
implement screen capturer for webrtc, and so I think it's right to add this
dependency in the content layer. Chrome itself doesn't depend on it directly or
indirectly (we use use it on the host side, which is not in chrome).
This library is used to implement chromoting host, so remoting/ seems like the
right place for it, but I'm open to moving it somewhere else. What do you think
would be a better place to put it? Somewhere in src/media? Would it be
acceptable to do it later in a separate CL, so this one doesn't block other CLs
I have that depend on this one?

 ]