From: "Roderick Taylor" <rtaylor@hcvwireless.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] SCO socket data transmission status
Date: Thu, 15 Jul 2004 09:52:26 +1000 [thread overview]
Message-ID: <opsa5i9odng1fi0r@trippin> (raw)
When you send to a SCO socket in BlueZ, is there a way to find out if the
bt device has transmitted the data you have written? Do SCO sockets have
any interaction with the select function?
To me it seems that sending to a bluez SCO socket will work no matter
what. If you send data to fast for the device to handle then, then the
data written will be ignored.
Is this a question for bluez-users rather than bluez-devel?
Rod.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-07-14 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 23:52 Roderick Taylor [this message]
2004-07-15 11:00 ` [Bluez-devel] SCO socket data transmission status 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=opsa5i9odng1fi0r@trippin \
--to=rtaylor@hcvwireless.com \
--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