On Thursday 06 January 2011 02:49:01 Will Thompson wrote: > On 04/01/11 18:35, Justin Karneges wrote: > > I think it's going to have to be (b). Clients assume a blank slate at > > session start, which is why the bare-jid unavailable works today in the > > way you'd expect. However, in general, I believe clients treat bare-jid > > presence as referring to a single session with a 0-length resource > > (residual effect of how legacy transports would send out resource-less > > presence). So, I would expect that existing behavior would be for the > > client to remove an empty session if it exists, but not to touch any > > other sessions. > > As a conflicting data point: telepathy-gabble forgets about any > resources' presence if it gets presence from a bare JID. (Presence of > any type, not just unavailable; in practice this is essentially > equivalent.)
Not just unavailable? What happens when you receive bare JID available presence then? All existing resources for the user are removed, and then a 0- length resource is added? -Justin
