Return-Path: Message-Id: <20FBD040-B040-43F0-9A1F-E5EF97DA9B85@gmail.com> From: Johan Hedberg To: BlueZ development In-Reply-To: <039f01c88a15$a848aaa0$6701a8c0@freqonedev> Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 20 Mar 2008 11:49:47 -0300 References: <1205440348.12951.9.camel@californication> <039f01c88a15$a848aaa0$6701a8c0@freqonedev> Subject: Re: [Bluez-devel] Moving towards a new API for BlueZ 4.0 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 David, On Mar 19, 2008, at 20:04, David Stockwell wrote: > > Any interest? Sure. The current code (mostly written by me) is something rather quickly put together to get the basic functionality in place. Especially the metadata transfer would be nice to get implemented since it's a mandatory feature for category 1 (player/recorder) devices in version 1.3 of the specification. > Who should I communicate with? In addition this list (as Marcel already mentioned) a good place to be in contact with the developers is the #bluez channel on irc.freenode.net. Johan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel