From: Vinicius Gomes <vinicius.gomes@openbossa.org>
To: Daniel Abraham <daniel.shrugged@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: obexd FTP server signals
Date: Sun, 18 Apr 2010 15:27:01 -0300 [thread overview]
Message-ID: <l2h2a9506371004181127g305febb5leb7392a54bb5692e@mail.gmail.com> (raw)
In-Reply-To: <x2q2c3916b71004180928s9778e8d8zdeebe9e350ae4a19@mail.gmail.com>
Hi Daniel,
On Sun, Apr 18, 2010 at 1:28 PM, Daniel Abraham
<daniel.shrugged@gmail.com> wrote:
> Hi, I have a question:
>
> Is there any way to get more transaction-related signals from obexd,
> when it's used as an FTP _server_?
>
No. At least, not yet.
> As far as I can see from "obexd-api.txt" and from dbus-monitor, the
> only things to catch are "session_started" and "session_removed".
>
> But I'd like to have a level of granularity similar to the FTP client:
> signals about starting/progress/canceling/completing transfers, which
> specific kinds of trasfers are done (list folder, get file, put file,
> etc.).
>
> Any ideas?
At first we considered some form of status reporting, but after
thinking and looking at other "file sharing" servers we noticed that
it was not really useful for the server to report that information,
for example, sshd and any ftp server, don't have any form of status
reporting.
In those cases only the client reports the status, because the client
is where the user has control. I don't think obexd is much different
from those servers.
But, do you have a concrete case for this?
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Cheers,
--
Vinicius
next prev parent reply other threads:[~2010-04-18 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 16:28 obexd FTP server signals Daniel Abraham
2010-04-18 18:27 ` Vinicius Gomes [this message]
2010-04-19 5:26 ` Daniel Abraham
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=l2h2a9506371004181127g305febb5leb7392a54bb5692e@mail.gmail.com \
--to=vinicius.gomes@openbossa.org \
--cc=daniel.shrugged@gmail.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 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).