From: "Udayan Singh" <udayan.singh@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] OBEX OPP/FTP implementation in Bluez
Date: Fri, 3 Aug 2007 00:10:39 +0530 [thread overview]
Message-ID: <d9a09df00708021140k58b2fc16gd7f5a868899017d9@mail.gmail.com> (raw)
In-Reply-To: <46B224A6.8040501@gmail.com>
Hi Manuel,
Thanks for the inputs, will check the same.
Also, probably you can update the wiki for bluez ??
http://wiki.bluez.org/wiki/Transfer
as well as roadmap:
http://wiki.bluez.org/wiki/Roadmap
I think it would be a good idea to do so !!
Regards,
Udayan
On 8/3/07, Manuel Naranjo <naranjo.manuel@gmail.com> wrote:
> Udayan,
> You should check OpenObex http://dev.zuckschwerdt.org/openobex/ it's a
> great obex implementation for Linux, I'm using it with bluez every day.
> Thanks,
> Manuel
> > 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 ?
> >
> > In case yes, which package should i look into else, if i am interested
> > in implementing the same, any views that you would like to share.
> >
> > Thanks,
> > Udayan
> >
> > -------------------------------------------------------------------------
> > 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
> >
> >
>
>
> -------------------------------------------------------------------------
> 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
>
-------------------------------------------------------------------------
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 18:40 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 [this message]
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
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=d9a09df00708021140k58b2fc16gd7f5a868899017d9@mail.gmail.com \
--to=udayan.singh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox