From: "YAO Ye" <yesiryao@qq.com>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Cc: marcel <marcel@holtmann.org>
Subject: openobex vs. obexd vs. obex-data-server
Date: Thu, 8 Jan 2009 20:07:14 +0800 [thread overview]
Message-ID: <tencent_3B1ED45643B84E67486BBA7F@qq.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Happy new year, everyone !
Thx for the great SW -- bluez !
I am a new user of bluez. My questions is about file transfer based on bluez.
what is the defference between: openobex, obexd, obex-data-server ?
I have porting bluez4 to my pxa310 handheld platform.
so, which one is the best/more suit one for me to use ?
----------
obex servers and clients:
Choose just one of these since they cannot be run at the same time.
obexd-0.8.tar.gz
obex-data-server-0.4.2.tar.gz
------------------
Email1: yesiryao@tom.com
Email2: yesiryao@qq.com
MSN : yesiryao@hotmail.com
[-- Attachment #2: Type: text/html, Size: 1092 bytes --]
next reply other threads:[~2009-01-08 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 12:07 YAO Ye [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-08 12:16 openobex vs. obexd vs. obex-data-server YAO Ye
2009-01-09 2:05 ` Liu, Raymond
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=tencent_3B1ED45643B84E67486BBA7F@qq.com \
--to=yesiryao@qq.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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