On Jan 16, 2008, at 8:21 AM, Peter Saint-Andre wrote:
Right. So caps is *just* disco, and then we define some new caps-
like protocol to encapsulate the OS+Software+Name+Version
information? Or do we stick that into entity capabilities using a
new hash?
I'm for:
a) putting it into a separate, large presence extension, that has all
of the information spelled out in as many languages as possible,
including client name, os name, os version, cpu speed, etc.
b) saying that if the sender doesn't include the information, you MUST
NOT query for it
c) we all agree not to implement the sending side
Seriously, we're talking about breaking a really good protocol for
information that is only mildly useful to the end user and has no
security implications, other than to leak info that the user might not
want leaked? If we just say "cache on a per-node basis, if you feel
the need to query for it", we're done, right?
(sorry for the snarky reply, i've had a long day)
--
Joe Hildebrand
