Return-Path: Message-ID: <457C2CF5.9040007@free.fr> Date: Sun, 10 Dec 2006 16:51:17 +0100 From: Fabien Chevalier MIME-Version: 1.0 To: BlueZ development References: <457655A2.6030001@xmission.com> In-Reply-To: <457655A2.6030001@xmission.com> Subject: Re: [Bluez-devel] org.bluez.Audio Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Brad & Marcel, I got a number of interrogations regarding the various methods/signals exposed here. I noticed a few things that won't work. To be able to pinpoint these issues one by one, i think there is a need to draw some diagrams that show the dynamic aspects of things. I'm gonna try drawing a few of those before the end of the year : hopefully i will find some spare time as i'm gonna be in hollidays from Xmas till new year... Cheers, Fabien > Marcel > > I rewrote the dbus proposal. If what's here looks ok we can start > thinking about the named pipe, ipc, or whatever we use for sending audio > and file descriptors around. > > http://bluetooth-alsa.sourceforge.net/future.html > > Brad > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel