From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Did not proceed with 2nd OBEX Connect request
Date: Mon, 05 Dec 2005 22:34:48 +0100 [thread overview]
Message-ID: <1133818488.4559.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20051205083440.79581.qmail@web32414.mail.mud.yahoo.com>
Hi Arch,
> Yes, you're right. There was no OBEX Connect request following the SDP
> service request. What I was trying to ask is that supposed to be,
> there is another OBEX Connect request following the SDP service
> request. However as you have seen in the hcidump trace, this did not
> happen. The normal flow of the Bluetooth transaction on the client
> side is that after the SDP service request, there will be a 2nd OBEX
> Connect request (without a prior OBEX Disconnect request for the 1st
> OBEX Connect request). In this regard, is there something in BlueZ
> that prevents this from happening?
additional SDP request can happen every time. For example to get
information about a status channel or something else. Check the
Bluetooth core or profile specifications for more details.
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:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 8:34 [Bluez-users] Did not proceed with 2nd OBEX Connect request Arch Sayo
2005-12-05 21:34 ` 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=1133818488.4559.7.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;
as well as URLs for NNTP newsgroup(s).