From: Brian Gix <bgix@codeaurora.org>
To: Jaganath <jaganath.k@samsung.com>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: FTP file authorization and transfer progress support
Date: Tue, 29 Nov 2011 22:45:49 -0800 [thread overview]
Message-ID: <4ED5D11D.1040709@codeaurora.org> (raw)
In-Reply-To: <B88DC7925BB14C2F8529CEC03B90B575@sisodomain.com>
Hi Jaganath,
On 11/29/2011 10:34 PM, Jaganath wrote:
> From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
>> On Tue, Nov 29, 2011 at 3:53 PM, Johan Hedberg
>> <johan.hedberg@gmail.com> wrote:
>>> 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.
>>
>> Im not so sure authorize here is really useful since FTP requires
>> connection authorization anyway, we can create transfers if the
>> purpose is to log them.
>
> Thanks for your reply.
> Even if FTP has connection authorization I think it is better to ask
> file authorization for put/get/delete. This gives more flexibility to
> application. It is up to application to decide whether to ask end user
> or simply accept. Also in put case if a file with same filename is already
> there, then this approach will be useful for application to handle that.
I think you may be confusing use cases.
If you are an FTP server, you are giving authorized remote users blanket
authority to read, write or browse, or some combination, your exposed
FTP file system. I suppose you could require additional
operation-by-operation request/confirm, but that would quickly make the
system very clumsy. It's not the usage model that FTP was designed for.
That is why we have the OPP profile, which is specifically for single
object sharing, and that has that kind of request/confirm model.
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-11-30 6:45 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
2011-11-29 14:16 ` Luiz Augusto von Dentz
2011-11-30 6:34 ` Jaganath
2011-11-30 6:45 ` Brian Gix [this message]
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=4ED5D11D.1040709@codeaurora.org \
--to=bgix@codeaurora.org \
--cc=jaganath.k@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).