Hi,
On Oct 6, 2008, at 5:12 PM, Jonathan Schleifer wrote:
We should have resources that are random and hidden from the user.
Not random, opaque, without meaning.
Sure, the server implementations should use something secure enough to
prevent presence leaks, but a clustered server might want to use
something like "cluster_id-session_id-sha1_sig": unique, "random" but
with some meaning *to the server* so that he can optimize routing.
The client should then show a list of connected resources, but
without the name.
Name for each connection can be provided using name attribute of Disco
<identity>.
The capabilities of the resource specify information like the
connection
yes.
or the hostname of the PC you are connected from
I'm assuming that this is the same as the optional name mentioned above.
(for example, I want to send something to resource Foobar because I
need that information there and not on Barfoo).
Sure, use <identity> name attribute to give "Desktop at office" or
"Server at home" human names.
So the client should present a list then, with the icon of the type
of resource and the hostname beneath it, if given. And all this
information should be hidden in caps.
Hidden not so much, Available via caps, yes.
Did I get it right?
Yeah, basically yes.
And yes, I know that I don't have much skin in the client game, so
this looks like work for you as a client developer :), I'm just
saying, this way is better :).
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
