From: Till Harbaum <harbaum@beecon.de>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: Moritz Gmelin <moritz.gmelin@avetana.de>
Subject: [Bluez-devel] Zero length L2CAP packets
Date: Thu, 10 Feb 2005 11:12:09 +0100 [thread overview]
Message-ID: <200502101112.09602.harbaum@beecon.de> (raw)
Hi,
while working on the avetana jsr82 implementation we discovered, that the bt
spec as well as jsr82 allow to transmit zero length l2cap packets. IMHO the
linux socket interface does not support zero length packets and a read
returning zero indicates an end of file (in this case meaning that the
connection has been closed).
What happens if the other side actually sends a zero length packet? Is this
dropped inside the kernel? Or will read return zero which i'll misinterpret
as the eof marker? How can i distinguish between eof and a zero length
packet?
Regards,
Till
--
Dr.-Ing. Till Harbaum Tel.: +49 721 4998963
BeeCon GmbH Fax: +49 721 4998962
Haid-und-Neu Strasse 7, 76131 Karlsruhe Mobil: +49 179 9087904
harbaum@beecon.de http://www.beecon.de
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-02-10 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 10:12 Till Harbaum [this message]
2005-02-10 14:04 ` [Bluez-devel] Zero length L2CAP packets Marcel Holtmann
[not found] ` <2def10fdd2a185bcddd4562929cd1417@avetana.de>
2005-02-22 0:17 ` Marcel Holtmann
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=200502101112.09602.harbaum@beecon.de \
--to=harbaum@beecon.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=moritz.gmelin@avetana.de \
/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