165
edits
Difference between revisions of "XMPP IM Client Design Guidelines"
Jump to navigation
Jump to search
XMPP IM Client Design Guidelines (view source)
Revision as of 09:24, 13 May 2015
, 09:24, 13 May 2015→Do not to encode any semantic into the resource
| Line 21: | Line 21: | ||
=== Rationale === | === Rationale === | ||
== Do not to encode any semantic into the resource == | == Do not to encode any semantic into the resource and don't specify a resource == | ||
=== Description === | === Description === | ||
Instead of letting the user specify a resource or providing a pre-configured list of possible resource names (e.g. '/home', '/work', '/notebook') [http://xmpp.org/rfcs/rfc6120.html#bind-servergen-success let the server generate a resource for your client]. You may optionally provide a possibility to configure the resource to the user under a "advanced settings" menu (or similar). But a XMPP user should not need to configure or specify a resource. | |||
=== Rationale === | === Rationale === | ||
Resource names should not be guessable to prevent [http://xmpp.org/rfcs/rfc6120.html#security-leaks-presence presence leaks]. | |||
== Show the type of a remote source (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource == | == Show the type of a remote source (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource == | ||