From: Matthias Schnelte <schnelte@uni-paderborn.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Several bluetooth dongles at time
Date: Fri, 11 Feb 2005 18:51:25 +0000 [thread overview]
Message-ID: <420CFEAD.2000202@uni-paderborn.de> (raw)
In-Reply-To: <1108039290.15974.33.camel@pegasus>
>>2) Can i have multiple connections on the same rfcomm channel? So more
>>than one mobile can connect to my server at time or only one device per
>>channel and i have to open more than one channel?
>
> One connection per RFCOMM channel. On the RFCOMM level there is no
> further multiplexing.
So, if I have two phones that provide one service each, but both on the
same rfcomm channel i will not be able to connect to both of them, right?
Why is that? I mean, it is all brought done to l2cap connections and
l2cap is not limited in that case.
Hmm, so the only solution is to use l2cap instead of rfcomm, right?
Matthias
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-11 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 12:19 [Bluez-devel] Several bluetooth dongles at time schnelte
2005-02-10 12:41 ` Marcel Holtmann
2005-02-10 13:10 ` [Bluez-devel] HCI Forwarding radeX
2005-02-10 14:47 ` Marcel Holtmann
2005-02-11 18:51 ` Matthias Schnelte [this message]
2005-02-11 19:03 ` [Bluez-devel] Several bluetooth dongles at time Marcel Holtmann
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=420CFEAD.2000202@uni-paderborn.de \
--to=schnelte@uni-paderborn.de \
--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.