From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateProxy usage?
Date: Mon, 31 Mar 2008 05:31:17 +0200 [thread overview]
Message-ID: <52DF986C-FC13-4F04-81F7-6A269B0EB0D1@holtmann.org> (raw)
In-Reply-To: <47F059B9.5030003@aircable.net>
Hi Manuel,
>> the proxy is what it is called. A proxy. So you need to have a
>> Unix,TCP or TTY server to connect to.
>>
> Ok good, what would be a TTY server in this case? I can imagine a TCP
> server, but a TTY server? Never heard of it.
in the most cases this is a hardware port. It can be emulated, but
that is not the usual case.
> Maybe it wasn't CreateProxy the one I should be using. I just need to
> create an RFcomm port, and then wait until someone connects to it,
> should I use createPort then?
You can't really do that over D-Bus. Use the native RFCOMM sockets
from the Bluetooth library.
Regards
Marcel
-------------------------------------------------------------------------
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 3:31 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 [this message]
2008-03-31 3:39 ` Manuel Naranjo
2008-03-31 3:56 ` Marcel Holtmann
2008-03-31 4:01 ` Manuel Naranjo
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=52DF986C-FC13-4F04-81F7-6A269B0EB0D1@holtmann.org \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox