linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Fiestas <afiestas@kde.org>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Specifying destination path in obexd/bluez-5
Date: Mon, 31 Dec 2012 09:56:50 +0100	[thread overview]
Message-ID: <13320115.C4qltrvZED@monsterbad> (raw)

Last time I tried to port KDE's obex support completely to obexd (we are 
already using obexd-client for opp sendfile) I couldn't complete it because 
there is no way of programatically specify the destination path of the 
incoming files, iirc using either ftp or opp.

Now checking out BlueZ-5 I'm not sure I see a way of doing it either.

So, is there anyway of changing the destination path programatically without 
having to restart obexd-server? If not, can I add a wish somewhere (bugrack?) 
for it? Would you consider?

Thanks and congratulations for BlueZ-5 :)!

             reply	other threads:[~2012-12-31  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31  8:56 Alex Fiestas [this message]
2012-12-31 10:01 ` Specifying destination path in obexd/bluez-5 Luiz Augusto von Dentz
2013-01-02 10:51   ` Alex Fiestas

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=13320115.C4qltrvZED@monsterbad \
    --to=afiestas@kde.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).