From: Manuel Naranjo <naranjo.manuel@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] OBEX OPP/FTP implementation in Bluez
Date: Thu, 02 Aug 2007 16:17:04 -0300 [thread overview]
Message-ID: <46B22DB0.60906@gmail.com> (raw)
In-Reply-To: <d9a09df00708021200r1df93be6leab6acc3680cc0da@mail.gmail.com>
Udayan Singh escribi=F3:
> Hi Manuel,
>
>
> =
>>> as well as roadmap:
>>> http://wiki.bluez.org/wiki/Roadmap
>>>
>>> =
>> I don't know if I can update this one, maybe in the feature BlueZ team
>> want to add obex support directly in the stack.
>> =
>
> So presently Bluez does not have obex support directly in the stack.
> If I want to work on the same, ne pointers to how can I go about doing
> the same ?
You can use openobex and obexftp (both are in the same place, openobex =
is a lib obexftp is an user app), it's the defacto obex implementation =
for linux and it works perfectly over bluetooth with bluez. It's just =
that you don't get this when you download blueZ.
What I'm not sure is that if the BlueZ guys are planning to reimplement =
Obex and add this to they're source base.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-02 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 18:25 [Bluez-devel] OBEX OPP/FTP implementation in Bluez Udayan Singh
2007-08-02 18:38 ` Manuel Naranjo
2007-08-02 18:40 ` Udayan Singh
2007-08-02 18:56 ` Manuel Naranjo
2007-08-02 19:00 ` Udayan Singh
2007-08-02 19:17 ` Manuel Naranjo [this message]
2007-08-06 16:08 ` Pierre-Yves Paulus
2007-08-02 19:17 ` Collin R. Mulliner
2007-08-02 21:10 ` Bastien Nocera
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=46B22DB0.60906@gmail.com \
--to=naranjo.manuel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.