#3431 HIGH Future : Need to be able to share objects in the mesh, not just activities

[Zarro Boogs per Child]

#3431: Need to be able to share objects in the mesh, not just activities
--------------------------+-------------------------------------------------
  Reporter:  kimquirk     |       Owner:  marco         
      Type:  enhancement  |      Status:  new           
  Priority:  high         |   Milestone:  Future Release
 Component:  sugar        |     Version:                
Resolution:               |    Keywords:                
  Verified:  0            |    Blocking:                
 Blockedby:               |  
--------------------------+-------------------------------------------------
Changes (by rwh):

 * cc: rwh (added)


Comment:

 I remember Eben writing something about this a short time ago, but I'm not
 sure where. Anyway, I thought about it as well, and I think it would
 ''not'' be a good idea to add things to the mesh view, since it is already
 crowded. Also, everybody advertising all their shared objects (somehow)
 and tracking them in the presenceservice sounds like a non-scalable idea:
 it will eat lots of resources on ''each'' machine. In this case doing
 queries sounds more appropriate than using notifications (IMO).

 I thought a nice solution would be to put a badge on buddies in the mesh
 view that are sharing objects. Then you can put a 'show objects' action in
 the palette. When activated, I would image something similar to the
 Journal object chooser to pop up where you select an object and download
 to the local Journal. This would give a coherent feeling between accessing
 one's own files and those of others.

 I think objects should be marked as shared in the Journal. The Journal
 activity would then have a simple webserver included that can be accessed
 through a stream tube. Retrieving index.xml gives a list of shared
 objects, used as the list for the object chooser. In this way the
 presenceservice would only have to know whether a buddy has any objects
 available.

 I think the chat activity will be heavily used, and kids will find out and
 tell each other quickly enough where they can get nice objects. So there
 ''probably'' is no real need to expose objects more directly. However,
 maybe in the friends view we could somehow place a list of the shared
 objects of friends. This model allows for a not too-complicated async
 search as well by doing simple http queries.

-- 
Ticket URL: <http://dev.laptop.org/ticket/3431#comment:17>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system