From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] decoding RFCOMM on hcidump -X -V
Date: Mon, 27 Feb 2006 00:52:24 +0100 [thread overview]
Message-ID: <1140997944.23559.15.camel@localhost> (raw)
In-Reply-To: <5f30e2610602261444m477c13b6m3667c3031e5cb298@mail.gmail.com>
Hi Jeff,
> Does Bluetooth's RFCOMM protocol have ACKs and a sliding window, like
> TCP? Is it possible for a sending application to block on send when
> sending a large payload to a slow reading application?
the RFCOMM is using flow control only. There is no sliding window and
thus no real ACK mechanism.
> I'm trying to debug a program I wrote using
> socket(PF_BLUETOOTH,SOCK_STREAM,BTPROTO_RFCOMM). Where can I learn
> more about decoding the output of `hcidump -X -V` especially as it
> applies to traffic crossing this RFCOMM socket? I am particularly
> interested in what to look for when chasing flow control and TCP-like
> reliability.
Since RFCOMM also has an MTU, you will see the packets going over the
air and the granted credits from each side.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-02-26 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 22:44 [Bluez-devel] decoding RFCOMM on hcidump -X -V Jeff Wilson
2006-02-26 23:52 ` 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=1140997944.23559.15.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 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).