[Standards-JIG] Roster block importing and synchronisationusingJEP-0093

Tijl Houtbeckers thoutbeckers at splendo.com
Tue Sep 14 23:28:50 UTC 2004

On Wed, 15 Sep 2004 00:21:43 +0100, Richard Dobson <richard at dobson-i.net>  

>> Well, this proposal relies on using existing clients and there existing  
>> features. No good client would just delete a "none" contact.
> That is a big assumption, there is no reason I can see that for  
> transport contacts you couldnt use the "none" status as an indication  
> that the user is no longer in the legacy contact list and thus it can be  
> automatically removed, I dont see where you get this idea that a "good  
> client" would never automatically delete a "none" contact, im not saying  
> that a client should always delete a "none" contact no matter wether its  
> a transport or not, but it makes perfect sence to me that this logic  
> could be used for transport contacts automatically, and if it isnt a  
> transport contact it makes sence that the user be prompted as to whether  
> they wish to remove this "ghost" contact or not to clean up the roster.

So what happens when I'm connected to the transport, and someone on the  
legacy network removes me?

More information about the Standards mailing list