#3551 NORM First D: closing Browse activity silently kills downloads-in-progress

[Zarro Boogs per Child]

#3551: closing Browse activity silently kills downloads-in-progress
--------------------------+-------------------------------------------------
  Reporter:  danw         |       Owner:  marco                 
      Type:  defect       |      Status:  new                   
  Priority:  normal       |   Milestone:  First Deployment, V1.0
 Component:  web browser  |     Version:                        
Resolution:               |    Keywords:                        
  Verified:  0            |  
--------------------------+-------------------------------------------------

Comment(by Eben):

 I think that this ticket and #3552 are really the same problem in that a
 good solution to either solves both.

 I don't think that background downloads, although potentially useful, is
 the way we should approach this.  It adds non-visible state to the system
 and makes things harder to keep track of.  Instead, I think we should
 embrace a pause/resume approach, which mimics the stop/resume of
 activities and Journal entries in general (as downloads are represented as
 in-progress entries).  Stopping a Browse session should simply pause any
 associated downloads.  Resuming the Browse session should unpause those
 downloads.  It should also be possible to unpause the download directly,
 which would have the effect of resuming the related Browse entry (this
 makes it impossible to lose track of the entry its associated with, which
 would otherwise make it impossible to unpause the download).

 If people agree with my comments on both tickets, this one should probably
 be closed as a duplicate.  I've also independently opened a ticket for
 resumable downloads: #3796.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3551#comment:6>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system