58
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 13:25, 14 June 2015
, 13:25, 14 June 2015→Rationale: Addition of the multiple same-client usecase.
Link Mauve (talk | contribs) (→Rationale: Addition of the multiple same-client usecase.) |
|||
| Line 38: | Line 38: | ||
Resource names should not be guessable to prevent [http://xmpp.org/rfcs/rfc6120.html#security-leaks-presence presence leaks (RFC 6120 13.10.2)]. | Resource names should not be guessable to prevent [http://xmpp.org/rfcs/rfc6120.html#security-leaks-presence presence leaks (RFC 6120 13.10.2)]. | ||
Providing a default resource also prevents the user from using the same software from two different locations at the same time. | |||
== Show the type and name of a resource (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource string itself == | == Show the type and name of a resource (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource string itself == | ||