From: Mingfan lu <lucharse@yahoo.com.cn>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] About the transfering speed of bluez RFCOMM socket
Date: Wed, 19 Jul 2006 01:51:07 -0700 (PDT) [thread overview]
Message-ID: <20060719085107.34521.qmail@web15806.mail.cnb.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 724 bytes --]
Env:
Machine A and machine B are the same.
But
suse10.1 for A ---bluez
windowsXP(SP2) for B ---bluesoleil
We use the same bluetooth dongle and mobile device(symbian) in the test.
When I use OpenObex(based on bluez Rfcomm socket) to send a file from machieA to the mobile device the transfering speed is about 10K BytePerSec.
When I use Bluesoleil to send the same file from machine B to the mobile device the transfering speed is about 40K-50K BytePerSec.
Why is B much better than A?
is it not efficient of Bluez Rfcomm socket? or other reason.
With respects,
Mingfan.Lu
---------------------------------
How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call rates.
[-- Attachment #1.2: Type: text/html, Size: 1245 bytes --]
[-- Attachment #2: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-07-19 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 8:51 Mingfan lu [this message]
2006-07-20 0:51 ` [Bluez-devel] About the transfering speed of bluez RFCOMM socket Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-07-20 7:19 Kamil Kamiński
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=20060719085107.34521.qmail@web15806.mail.cnb.yahoo.com \
--to=lucharse@yahoo.com.cn \
--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