#8699 NORM Future : Work around presence bugs

[Zarro Boogs per Child]

#8699: Work around presence bugs
----------------------------+-----------------------------------------------
 Reporter:  bert            |         Owner:  etoys         
     Type:  defect          |        Status:  new           
 Priority:  normal          |     Milestone:  Future Release
Component:  etoys-activity  |       Version:  not specified 
 Keywords:                  |   Next_action:  code          
 Verified:  0               |     Blockedby:                
 Blocking:                  |  
----------------------------+-----------------------------------------------
 Sometimes the presence service delivers malformed data, which makes Etoys
 show an unpleasant error dialog.

 The scenario goes like this: two XOs connected to same access point, but
 in the neighborhood view only one can see the other. Trying to share
 anyway makes the shared activity appear in only one XO's neighborhood.
 Joining it works fine, also the Joined() signal for the remote buddy is
 delivered, but accessing the joined buddy's properties gets all blank
 strings, in particular no key. But shortly after that we receive a tube
 which does have a valid buddy key (Etoys is fortunately putting it into
 the tube properties). From that info we could construct a dummy buddy
 because the key and tube address is really all we need to communicate
 back.

 Last seen in joyride-2489.

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