All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iain Hibbert <plunky@rya-online.net>
To: GianPiero Puccioni <gianpiero.puccioni@isc.cnr.it>
Cc: "Li\, Zhigang" <zhigang.li@intel.com>,
	"linux-bluetooth\@vger\.kernel\.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: Obex Push
Date: Wed, 11 Feb 2009 11:24:15 +0000 (GMT)	[thread overview]
Message-ID: <1234351455.708556.26913.nullmailer@galant.ukfsn.org> (raw)
In-Reply-To: <4992A7A4.1010802@isc.cnr.it>

On Wed, 11 Feb 2009, GianPiero Puccioni wrote:

> Li, Zhigang wrote:
>
> .....
>
> >> I have seen it but I don't know python, in fact I forgot to say the program should be
> >>  a small command line C program, something like "opush  00:11:9F:4B:A1:D9 text.txt"
> >> as I have to use it in bash script.
> > ./send-files [target address] /home/text.txt
> >
> Unfortunately I cannot use it as I cannot compile obexd (my linux is a little outdated and
> my libglib is too old). That's why I was trying to write my own C prog as I used Bluez
> before for another project.

you could use 'obexftp' or 'obexapp' either directly or as examples to do
this, both use 'openobex' library. See

	http://openobex.triq.net/
	http://www.geocities.com/m_evmenkin/

(obexapp was written for FreeBSD and provides server capability also but
perhaps it would be possible to adapt it to bluez..)

iain

  reply	other threads:[~2009-02-11 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  9:23 Obex Push GianPiero Puccioni
2009-02-11 10:00 ` Li, Zhigang
2009-02-11 10:11   ` GianPiero Puccioni
2009-02-11 10:14     ` Li, Zhigang
2009-02-11 10:25       ` GianPiero Puccioni
2009-02-11 11:24         ` Iain Hibbert [this message]
2009-02-11 11:25       ` GianPiero Puccioni
2009-02-11 11:53         ` Thierry Pierret
2009-02-12  1:24 ` Yao Ye
2009-02-11 10:47 Thierry Pierret

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=1234351455.708556.26913.nullmailer@galant.ukfsn.org \
    --to=plunky@rya-online.net \
    --cc=gianpiero.puccioni@isc.cnr.it \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zhigang.li@intel.com \
    /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.