#7963 NORM 9.1.0: Handling of new user info data

[Zarro Boogs per Child]

#7963: Handling of new user info data
----------------------------+-----------------------------------------------
 Reporter:  epmfairweather  |         Owner:  ypod         
     Type:  defect          |        Status:  new          
 Priority:  normal          |     Milestone:  9.1.0        
Component:  cerebro         |       Version:  not specified
 Keywords:                  |   Next_action:  never set    
 Verified:  0               |     Blockedby:               
 Blocking:                  |  
----------------------------+-----------------------------------------------
 The new_node parameter of the on_node_info_arrival signal seems to return
 a boolean value as to whether the info for the node was already stored in
 the shared activity structure or not. If this is the intention then this
 parameter should be of the D-Bus boolean type not 32-bit integer.

 In addition this parameter currently always return false, as the info is
 added to the structure before the test of its presence there is performed.
 (This also means that no activities registered by other nodes seem to be
 added to the shared activity structure, let alone that the activity
 registration is signalled. (See http://dev.laptop.org/ticket/7714))

 In any case this parameter's value seems to be of limited use. What would
 be more useful would be an indication of what user info was new or had
 changed rather than the user having to determine this by themself from the
 large JSON encoded dictionary of info provided by the first parameter.

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