Piping for audio decoding.

remoting/client/client_context.h

Index: remoting/client/client_context.h
diff --git a/remoting/client/client_context.h b/remoting/client/client_context.h
index 27a44162d3eaa402928ea48ca661e674231b2af8..19c36f3c3564d7654d9561e81100a237b244a721 100644
--- a/remoting/client/client_context.h
+++ b/remoting/client/client_context.h
@@ -29,13 +29,17 @@ class ClientContext {
 
   base::SingleThreadTaskRunner* main_task_runner();
   base::SingleThreadTaskRunner* decode_task_runner();

[Wez, 2012/08/07 18:29:05]

nit: video_decode_task_runner()

+  base::SingleThreadTaskRunner* audio_decode_task_runner();

[Wez, 2012/08/07 18:29:05]

What is the intent in running audio decode on a separate thread from video
decode? Most client devices will have a limited number of cores, and we're
already running VP8 decode mutli-threaded, so except on high-end systems an
additional thread just adds scheduling overhead. Is the aim to ensure that long
video decodes don't block audio decode for too long, for example?

 
  private:
   scoped_refptr<base::SingleThreadTaskRunner> main_task_runner_;
 
-  // A thread that handles all decode operations.
+  // A thread that handles all video decode operations.
   base::Thread decode_thread_;
 
+  // A thread that handles all audio decode operations.
+  base::Thread audio_decode_thread_;
+
   DISALLOW_COPY_AND_ASSIGN(ClientContext);
 };