[SyncEvolution] SetPeer behaviour.

Hi Folks, In terms of the PIM manager API, specifically: "void SetPeer(string uid, dict properties) Adds or modifies a peer. Modifying a peer does *not* affect any contact data which might be cached for it. " And a peer itself characterised as a combination of [protocol, transport, address, database, logdir, maxsessions] I wonder if one modifies some of these keys should the behaviour in fact *affect* any contact data which might be cached. For instance, if we change the BT address for a previously PBAP synchronised phone, and we then come and change the BT address to something different for that unique uid, should the contact data not be invalidated? Generally, should some properties of a peer be immutable? Perhaps I'm miss interpreting the API description? Warm Regards Tom. -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.