After comparing the out-of-the-box setting.txt vs. yours I see where the cid.info was expected to contain the name information. It also illustrates how the desktop's pixel grid can be individually addressed so bits and pieces of information can be collected from various xap sources and displayed as related information. The other Kevin also illustrated that the Slimp3 did not have this degree of access freedom for its display and another xap application was needed to collect and forward to the Slimp3. In this later case the issues of timing tradeoffs need to be tweaked to know how long to wait for the name before sending the payload to the Slimp3.
Since the UK does not have Name information in the Telco CID stream it tends to weight the architectural solution to different providers for the name. With name sometimes available in the CID stream and sometimes available in the database then the decision on how to merge the two potential sources is a little trickier. My decision was to make the CID.Incomming sender load the database of information into its local cache from all the potential database sources during its initialization. This way it has all information available in the system when the telco stream appears.
Since the UK does not have Name information in the Telco CID stream it tends to weight the architectural solution to different providers for the name. With name sometimes available in the CID stream and sometimes available in the database then the decision on how to merge the two potential sources is a little trickier. My decision was to make the CID.Incomming sender load the database of information into its local cache from all the potential database sources during its initialization. This way it has all information available in the system when the telco stream appears.
Comment