From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jaganath <jaganath.k@samsung.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: FTP file authorization and transfer progress support
Date: Tue, 29 Nov 2011 15:53:38 +0200 [thread overview]
Message-ID: <20111129135338.GA31479@x220> (raw)
In-Reply-To: <4928F261E93B4ADD83272E364EF54224@sisodomain.com>
Hi Jaganath,
On Tue, Nov 29, 2011, Jaganath wrote:
> Currently in OBEXD, only OPP put has authorization and file progress
> indication. I am planning to implement the same in FTP put/get/delete the
> same way as it does in OPP. But application may need to know the type of the
> obex operation to which the Authorize method is invoked. So I am planning to
> add a new method namely GetProperties in transfer, which returns the type of
> the operation (put/get/delete) so that application can use it in Authorize
> method. Please let me know your suggestions.
We try to avoid such extra round-trips in our D-Bus APIs. If such a
feature is really needed the essential context information should be
provided as parameters to the "authorize" call.
Johan
next prev parent reply other threads:[~2011-11-29 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 9:27 metadata dbus sathish
2011-11-29 11:26 ` Luiz Augusto von Dentz
2011-11-29 11:39 ` sathish
2011-11-29 12:00 ` Luiz Augusto von Dentz
2011-11-29 12:22 ` sathish
2011-11-29 13:43 ` FTP file authorization and transfer progress support Jaganath
2011-11-29 13:53 ` Johan Hedberg [this message]
2011-11-29 14:16 ` Luiz Augusto von Dentz
2011-11-30 6:34 ` Jaganath
2011-11-30 6:45 ` Brian Gix
2011-11-30 6:50 ` Hendrik Sattler
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=20111129135338.GA31479@x220 \
--to=johan.hedberg@gmail.com \
--cc=jaganath.k@samsung.com \
--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 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.