[Standards] rfc3921bis: self-presence
Jonathan Chayce Dickinson
chayce.za at gmail.com
Wed Aug 29 17:03:37 UTC 2007
Rachel Blackman wrote:
>> Is it harmful for the "baz" resource to receive its self-presence? I
>> don't see a particular reason why the server needs to avoid sending
>> that. Would it confuse the client?
> No. And frankly, it is annoying NOT to get the presence, because then
> you have to add special-case code to your roster for any users who DO
> want their own JID there. So that every time you change your own
> status, you have to go look up if your own JID is on your roster and
> generate an event just like a presence change for it. Hardly a
> disaster, but makes the status stuff messier than necessary.
Yes, very annoying, but server administrators are far more aware of
changes to XMPP than your average Joe user. A client using some old
version of software will be plagued by this little mis-hap. Chances are
once the server code changes, any servers that deploy it will be soon to
follow. Maybe there is another way?
Maybe the server could only send a client's presence back to him if it
has changed since the server last sent it?
jonathan chayce dickinson
email: chayce.za at gmail.com
jabber: moitoi at inflecto.org
<some profound piece of wisdom>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6974 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards