On Wed, Apr 10, 2013 at 1:41 AM, M.S. Suraj <mssurajkaiga gmail com> wrote:There is no decision on this yet but as I said, based on that
> Thank you for the quick reply. I wasn't aware about libsoup and am currently
> going through its APIs. I read the comments and the discussion posted below
> it.
>
> But I'm not sure about the D-Bus interface. Will the download take place in
> the browser/app that requested it, or will it be transferred to Transfers?
discussion I think we should go for former.
Exactly.
> I
> would prefer the latter but then again, we would face the problem of
> transferring credentials to Transfers.
I don't think we need to control that and even if we do, this control
> On the other hand, if the download
> takes place in the browser/app itself, then all we need to do is query for
> current status of the ongoing downloads and update the notification tray,
> but this would not give Transfers much control over the download (like
> setting speed/bandwidth limit
can also be exposed over D-Bus by the apps.
>, pausing/restarting downloads)
Same here, it can be easily exposed over D-Bus.
Yes but apps can be split into backend and UI so then only backend
> and also we
> would need the application to be running until the download finishes.
needs to be running, some apps already are AFAIK. Another (much
simpler to implement) solution could be for apps to hide their UI
rather than exiting the application completely if user quits the UI
while a transfer is in progress. If user launches the app again, the
UI is shown again.
--
Regards,
Zeeshan Ali (Khattak)
FSF member#5124