From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] RFCOMM disconnect command from slave device
Date: Mon, 05 Dec 2005 22:32:49 +0100 [thread overview]
Message-ID: <1133818369.4559.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20051205103257.18037.qmail@web32409.mail.mud.yahoo.com>
Hi Arch,
> I would like to ask if it is okay for a slave device to be the first
> to issue a disconnect command in the RFCOMM layer rather than the
> master device. Usually, after the OBEX Disconnect request of the
> master device and the corresponding response of the slave device, the
> master issues a disconnect command in the RFCOMM layer. However, the
> slave device (running on BlueZ) is the first one to issue a disconnect
> command in the RFCOMM layer, and the master device issues a disconnect
> command (RFCOMM) after that of the slave device. Is this okay?
I don't see any problem with that and so far there were no problems at
all. However the ownership of connections is something that is unclear
within the Bluetooth specification.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-12-05 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 10:32 [Bluez-users] RFCOMM disconnect command from slave device Arch Sayo
2005-12-05 21:32 ` 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=1133818369.4559.5.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-users@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