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:34, 13 May 2015
, 09:34, 13 May 2015→Show the type of a remote source (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource
| (One intermediate revision by the same user not shown) | |||
| Line 21: | Line 21: | ||
=== Rationale === | === Rationale === | ||
== Do not to encode any | == Do not to encode any semantics into the resource and don't specify a resource == | ||
=== Description === | === Description === | ||
| Line 31: | Line 31: | ||
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)]. | ||
== Show the type of a remote | == Show the type of a remote resource (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource == | ||
=== Description === | === Description === | ||
Users want to know the type of a remote resource, e.g. "Is this the resource of my friends mobile device or of his desktop?". Clients should display the type using the 'identity' information provided by [http://xmpp.org/extensions/xep-0030.html#info-basic XEP-30 disco#info] query results. So instead of having a resource like '/work-pc', the client should return | |||
<pre name='xml'> | |||
<identity | |||
category='client' | |||
type='pc' | |||
name='Work PC'/> | |||
</pre> | |||
within the 'disco#info' results. | |||
=== Rationale === | === Rationale === | ||
Encoding semantic in the value of the resource is not recommend (see previous item). | |||