From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SDP & RFCOMM SYNC
Date: Fri, 07 Jan 2005 15:27:21 +0100 [thread overview]
Message-ID: <1105108041.4299.100.camel@pegasus> (raw)
In-Reply-To: <5000105b05010705172040f6c3@mail.gmail.com>
Hi Amit,
> can u explain how it is possible?
>
> Because only one l2cap connection is possible over a ACL connection
> (between 2 devices).
who said so? There can only be one ACL connection between two devices,
but there is no limit for L2CAP connections. You can even have multiple
connections on the same PSM.
> According to SDP specification, SDP seesion first issue a SDP connect,
> send SDP query, wait for response and then send SDP disconnect.
>
> if we start a SDP session, What will happen with the l2cap
> connection, over which 1( or more ) rfcomm session is running?
>
> Should l2cap implementation provide a support for this or SDP should
> check for that?
>
> if so how to implement this at the l2cap level?
Read the specification and look at the source code. As I said, this
simply works.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-01-07 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 9:38 [Bluez-devel] SDP & RFCOMM SYNC Amit Kumar Goel
2005-01-07 12:55 ` Marcel Holtmann
2005-01-07 13:17 ` Amit Kumar Goel
2005-01-07 13:38 ` Peter Wippich
2005-01-07 13:54 ` [Bluez-devel] headset emulator apps Nelson Murilo
2005-01-07 18:27 ` Brad Midgley
2005-01-07 18:37 ` Nelson Murilo
2005-01-07 14:27 ` Marcel Holtmann [this message]
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=1105108041.4299.100.camel@pegasus \
--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