#2555 BLOC Trial-3: Journal needs to notify progress of entry operations

[Zarro Boogs per Child]

#2555: Journal needs to notify progress of entry operations
-------------------------------+--------------------------------------------
  Reporter:  tomeu             |       Owner:  tomeu  
      Type:  defect            |      Status:  new    
  Priority:  blocker           |   Milestone:  Trial-3
 Component:  journal-activity  |     Version:         
Resolution:                    |    Keywords:         
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by tomeu):

  * priority:  normal => blocker
  * summary:  Journal needs in-progress entry API => Journal needs to
              notify progress of entry operations

Comment:

 This depends on #2761 for normal copies between mount points and for
 saving to the journal of heavy activity instances.

 For downloads, we still have to find a way of doing this.

 Right now, downloads end up in the datastore after going through two
 stages:

  1. Download itself. Mozilla reports the progress of the download.
  2. Copy to the datastore internal storage area. No progress is yet
 reported.

 When downloading a large pdf (for example 35MB), the download itself will
 take some time, and the subsequent copy to flash would take approx. 25s.
 We need to give the user a view of when he can expect the download will be
 completed, including the time of copying it to the DS.

 If the download was done directly to the same filesystem as the main mount
 point (internal flash), we could save those 25s. provided that the DS
 moves the file instead of duplicating it (#2763). Then, it would be
 sufficient with reporting the download progress as mozilla tells us,
 simplifying quite a bit the problem.

-- 
Ticket URL: <https://dev.laptop.org/ticket/2555#comment:3>
One Laptop Per Child <http://laptop.org/>