From: nobilet <stephane.nobilet@sacet.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] OBEX data rate
Date: Tue, 10 Jan 2006 18:44:51 +0100 [thread overview]
Message-ID: <43C3F293.2030006@sacet.com> (raw)
Hi,
Is it possible to obtain the instantaneous data rate of a file transfer
between two bluetooth devices on OBEX ?
Otherwise, which process manage the event callback of the OBEX layer ?
When an OBEX event occurs, like OBEX_EV_PROGRESS in the program
obex_test, how many bytes are transmitted ?
Thank you very much for your answers.
Regards.
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-01-10 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 17:44 nobilet [this message]
2006-01-11 14:38 ` [Bluez-devel] OBEX data rate 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=43C3F293.2030006@sacet.com \
--to=stephane.nobilet@sacet.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;
as well as URLs for NNTP newsgroup(s).