Linux bluetooth development
 help / color / mirror / Atom feed
From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: [PATCH obexd v0] client-doc: Guarantee prefix in transfer paths
Date: Tue, 21 Aug 2012 09:23:35 +0200	[thread overview]
Message-ID: <1345533815-5611-1-git-send-email-mikel.astiz.oss@gmail.com> (raw)

From: Mikel Astiz <mikel.astiz@bmw-carit.de>

The client D-Bus documentation should mention that all transfer paths
contain a prefix consisting of the path of the session they belong to.

This can be conveniently used by clients to install D-Bus signal matches
that concentrate on the relevant signals.
---
 doc/client-api.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/doc/client-api.txt b/doc/client-api.txt
index 839a78c..7ca65cc 100644
--- a/doc/client-api.txt
+++ b/doc/client-api.txt
@@ -466,7 +466,7 @@ Transfer hierarchy
 
 Service		org.bluez.obex.client
 Interface	org.bluez.obex.Transfer
-Object path	[variable prefix]/{transfer0,transfer1,...}
+Object path	[variable prefix]/{session0,session1,...}/{transfer0,...}
 
 Methods		dict GetProperties()
 
-- 
1.7.7.6


             reply	other threads:[~2012-08-21  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  7:23 Mikel Astiz [this message]
2012-08-21  8:31 ` [PATCH obexd v0] client-doc: Guarantee prefix in transfer paths Patrick Ohly
2012-08-21 11:41   ` Mikel Astiz
2012-08-21 12:08     ` Marcel Holtmann
2012-08-21 12:15       ` Mikel Astiz
2012-08-22 11:39   ` Luiz Augusto von Dentz
2012-08-22 12:04     ` Patrick Ohly
2012-08-22 12:42       ` Mikel Astiz
2012-08-22 12:52       ` Luiz Augusto von Dentz
2012-08-22 16:19         ` Patrick Ohly
2012-08-27  7:00 ` Luiz Augusto von Dentz

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=1345533815-5611-1-git-send-email-mikel.astiz.oss@gmail.com \
    --to=mikel.astiz.oss@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz@bmw-carit.de \
    /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