On 14 May 2010, at 00:18, Randy Watler wrote: > Hey Gang, > > I noticed that SharedData and Participant are keyed back to the Widget using > the GUID field. This is in contrast to the preponderance of the persistent > data which is keyed to Widget via its object id. I assume there is no > objection to unifying this for all Widget relationships and using the object > id. Otherwise, let me know if the use of GUID for SharedData and Participant > was by design and I missed something along the way. Thanks!
The "sibling" definition for shared data and participants uses the rule of "same widget in same context". Now this could be keyed on Widget ID rather than Widget GUID if we can guarantee the stability of the ID - I think keying on GUID is simply because this should always be the same, even if the widget is unloaded and then reinstalled and gets another ID. However I don't think this should really be a problem, so keying on the ID should be fine. Unless Paul can think of a reason why we still need to do it this way? > > Randy >
