From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateProxy usage?
Date: Mon, 31 Mar 2008 01:01:19 -0300 [thread overview]
Message-ID: <47F0620F.8020606@aircable.net> (raw)
In-Reply-To: <CA77AEF1-2E8A-4EDB-A806-563338C34565@holtmann.org>
> 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
next prev parent reply other threads:[~2008-03-31 4:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 2:52 [Bluez-devel] CreateProxy usage? Manuel Naranjo
2008-03-31 3:20 ` Marcel Holtmann
2008-03-31 3:25 ` Manuel Naranjo
2008-03-31 3:31 ` Marcel Holtmann
2008-03-31 3:39 ` Manuel Naranjo
2008-03-31 3:56 ` Marcel Holtmann
2008-03-31 4:01 ` Manuel Naranjo [this message]
2008-03-31 4:09 ` Marcel Holtmann
2008-03-31 13:58 ` Manuel Naranjo
2008-03-31 4:04 ` Denis KENZIOR
2008-03-31 13:33 ` Manuel Naranjo
2008-04-02 16:05 ` Pierre-Yves Paulus
2008-04-02 16:13 ` Manuel Naranjo
2008-04-02 16:22 ` Pierre-Yves Paulus
2008-04-02 23:37 ` Denis KENZIOR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47F0620F.8020606@aircable.net \
--to=manuel@aircable.net \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.