From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Serial comunication RFCOMM
Date: Wed, 05 Jul 2006 00:54:36 +0200 [thread overview]
Message-ID: <1152053676.29250.4.camel@localhost> (raw)
In-Reply-To: <e1effdeb0607041532x5701ab2eib524b5c70f0dc436@mail.gmail.com>
Hi Claudio,
> sorry. Just fixing a wrong answer. I read the question quickly without
> pay attention exactly what you asked :-) According with the spec you
> can have up to 7 ACL connections. Between two BT devices, the RFCOMM
> protocol supports up to 60 simultaneous connections , I never tested
> and probably linux should have a limitation. I guess Marcel can answer
> this better.
there are no limitations. Except that it is 30 in one and 30 in the
other direction for RFCOMM. For L2CAP you can even do more connections
as long as the kernel has memory to store them.
Regards
Marcel
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-04 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 10:37 [Bluez-devel] Serial comunication RFCOMM Victor Andres
2006-07-03 12:29 ` Peter Wippich
2006-07-03 12:46 ` Claudio Takahasi
2006-07-03 15:56 ` Victor Andres
2006-07-04 18:09 ` Victor Andres
2006-07-04 18:56 ` Claudio Takahasi
2006-07-04 22:32 ` Claudio Takahasi
2006-07-04 22:54 ` Marcel Holtmann [this message]
2006-07-05 12:23 ` Victor Andres
2006-07-05 12:34 ` Marcel Holtmann
2006-07-05 12:46 ` Peter Wippich
2006-07-05 13:07 ` Marcel Holtmann
2006-07-05 12:38 ` Peter Wippich
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=1152053676.29250.4.camel@localhost \
--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 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.