#2240 HIGH Untriag: resuming activity from journal when activity is running should resume that running instance

[Zarro Boogs per Child]

#2240: resuming activity from journal when activity is running should resume that
running instance
---------------------+------------------------------------------------------
  Reporter:  erikb   |       Owner:  marco    
      Type:  defect  |      Status:  new      
  Priority:  high    |   Milestone:  Untriaged
 Component:  sugar   |     Version:           
Resolution:          |    Keywords:           
  Verified:  1       |  
---------------------+------------------------------------------------------
Changes (by Eben):

  * priority:  normal => high
  * verified:  0 => 1
  * component:  journal-activity => sugar

Comment:

 This is indeed a bug.  We need to consider the unique ID for the given
 activity and its version ID when resuming.  We must compare these IDs
 locally, to be sure that the activity isn't already running (as in the
 provided example above), but we must also check to be sure that an
 activity with matching IDs isn't already present on the mesh;  When it is,
 we must initiate a join on the mesh activity instead.

 I don't know the details, but ideally this will operate as a service of
 Sugar when a request to open an activity is generated, and not actually
 wrapped into the Journal itself.  I imagine there will be many instances
 which require this uniqueness check, such as resuming a file in the
 Clipboard, on a BBoard, when receiving an invitation, etc.  We should
 generalize as much as possible.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2240#comment:2>
One Laptop Per Child <http://laptop.org/>