From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] OBEX OPP/FTP implementation in Bluez
Date: Thu, 02 Aug 2007 22:10:35 +0100 [thread overview]
Message-ID: <1186089035.3908.2.camel@snoogens.fab.redhat.com> (raw)
In-Reply-To: <d9a09df00708021125n3abd1281l51d7f313e913da27@mail.gmail.com>
On Thu, 2007-08-02 at 23:55 +0530, Udayan Singh wrote:
> Hi All,
>
> Had been going through the link of bluez wiki. On the following page:
> http://wiki.bluez.org/wiki/Roadmap
> ----------------------------
> .....
> This page lists planed features, changes, etc to BlueZ in the future.
> ......
> Transfer service
> Obex Object Push Profile (OPP)
> Obex File Transfer Profile (FTP)
> ....
> ----------------------------
> So, isnt this implemented as of now ?
Will be in openobex itself, once Tadas finishes his Google Summer of
Code project (look on Google's page, under the GNOME project).
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-08-02 21:10 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
2007-08-06 16:08 ` Pierre-Yves Paulus
2007-08-02 19:17 ` Collin R. Mulliner
2007-08-02 21:10 ` Bastien Nocera [this message]
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=1186089035.3908.2.camel@snoogens.fab.redhat.com \
--to=hadess@hadess.net \
--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