Linux bluetooth development
 help / color / mirror / Atom feed
From: "Thierry Pierret" <tpi@qspin.be>
To: "Liu, Raymond" <raymond.liu@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Obexd 0.8 : howto
Date: Wed, 14 Jan 2009 10:48:22 +0100	[thread overview]
Message-ID: <e6fea9c20901140148k55c1c5f8i6e1a65878e69f803@mail.gmail.com> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E04839CD5@pdsmsx502.ccr.corp.intel.com>

>        Well, under OBEXD 0.8, you can use test/send-files to verify that is your whole env. is setting correctly for the obexd and OPP profile. Though I know you are not comfortable with python, but this is the quickest way to verify it. And there is an API doc at doc/client-api.txt

The mentioned files are indeed the ones I use as documentation.
Finaly, Python is not so complicated to read and to understand ;-)

>        And what's your meaning for using dbus commands? You mean using libdbus or using dbus-send? For using libdbus or dbus's glib binding, I guess you can also read Meamo's tutorial doc for some example.  And for using dbus-send, it's a little bit complicate to send a dict as input parameter to dbus, man dbus-send is a good start. But actually using Python will be easier :)

Python is not installed on the platform I'm testing. That's the reason
why I could not use the test samples and I'm attempting to test the
bluetooth features with the dbus-send command. And as you said, I'm
stucked with the dict parameter. I think I will have to install Python
anyway.

> Raymond

Thanks for your answer.

Does anyone have an idea for the 1st of my questions : why any attempt
to push a file to the obexd server fails with a "HUP" message ?

Thierry

      reply	other threads:[~2009-01-14  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 13:35 Obexd 0.8 : howto Thierry Pierret
2009-01-14  2:14 ` Liu, Raymond
2009-01-14  9:48   ` Thierry Pierret [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=e6fea9c20901140148k55c1c5f8i6e1a65878e69f803@mail.gmail.com \
    --to=tpi@qspin.be \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=raymond.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox