Return-Path: Message-ID: <47F0620F.8020606@aircable.net> Date: Mon, 31 Mar 2008 01:01:19 -0300 From: Manuel Naranjo MIME-Version: 1.0 To: BlueZ development References: <47EDAEED.4000302@aircable.net> <47F059B9.5030003@aircable.net> <52DF986C-FC13-4F04-81F7-6A269B0EB0D1@holtmann.org> <47F05CEF.8040300@aircable.net> In-Reply-To: Subject: Re: [Bluez-devel] CreateProxy usage? 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 > how do you wanna transfer the data? D-Bus is not for data transfer Via a dev file the same way the rfcomm tool does, we just create /dev/rfcomm# or maybe new socket? I think the main idea is hiding the hole socket functionality, so maybe creating a new socket for accessing to the established connection doesn't make any sense. But maybe creating a node on runtime and then telling the programmer over d-bus that the connection status makes sense. Ideas? I don't think I'm fully out of the path. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel