From 1e2dd6f46c6f5b455acd66034de47db2e501a3f1 Mon Sep 17 00:00:00 2001
From: Stein Magnus Jodal <stein.magnus@jodal.no>
Date: Wed, 11 Aug 2010 22:57:12 +0200
Subject: [PATCH] Backend API: Add optional argument 'output_connection' to
 BaseBackend constructor

---
 docs/changes.rst                 | 3 +++
 mopidy/backends/base/__init__.py | 6 +++++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/changes.rst b/docs/changes.rst
index c8e4c912..811eb482 100644
--- a/docs/changes.rst
+++ b/docs/changes.rst
@@ -35,6 +35,9 @@ Another great release.
   - :meth:`mopidy.backends.base.BaseLibraryController.search()` now accepts
     keyword arguments of the form ``search(artist=['foo', 'fighters'],
     album=['bar', 'grooves'])``.
+  - :meth:`mopidy.backends.base.BaseBackend()` now accepts an
+    ``output_connection`` which it can use to send messages (i.e. audio data)
+    to the output process.
 
 
 
diff --git a/mopidy/backends/base/__init__.py b/mopidy/backends/base/__init__.py
index e79aceae..942b190e 100644
--- a/mopidy/backends/base/__init__.py
+++ b/mopidy/backends/base/__init__.py
@@ -23,13 +23,17 @@ class BaseBackend(object):
     :param core_queue: a queue for sending messages to
         :class:`mopidy.process.CoreProcess`
     :type core_queue: :class:`multiprocessing.Queue`
+    :param output_connection: a connection for sending messages to the
+        output process
+    :type output_connection: :class:`multiprocessing.Connection`
     :param mixer: either a mixer instance, or :class:`None` to use the mixer
         defined in settings
     :type mixer: :class:`mopidy.mixers.BaseMixer` or :class:`None`
     """
 
-    def __init__(self, core_queue=None, mixer=None):
+    def __init__(self, core_queue=None, output_connection=None, mixer=None):
         self.core_queue = core_queue
+        self.output_connection = output_connection
         if mixer is not None:
             self.mixer = mixer
         else: