My initial instinct is to add another hash to presence, which is
resolved with
an iq:version query. Arguably, a hash might be even longer than
client +
version + os combined, so maybe just putting iq:version content into
presence
would be enough.
My thought is that if there's a simple way to pick up the version
information and cache in an intelligent manner, then better to rely on
the clients interested in that to download the information.
If not -- if, for instance, we want this still to be JID+node specific
-- then I'd rather just put a simple client display name (the version
can even be part of the display name) into the presence; if it's
there, clients that care about it can display it, and if it's not, we
can safely assume the client doesn't want that sort of information
displayed.
--
Rachel Blackman <[EMAIL PROTECTED]>
Trillian Messenger - http://www.trillianastra.com/