Difference between revisions of "XMPP IM Client Design Guidelines"
| Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
= Advices = | = Advices And Recommendations = | ||
== Do not to split up JIDs into multiple input fields == | == Do not to split up JIDs into multiple input fields == | ||
Revision as of 09:37, 13 May 2015
Introduction
Advices And Recommendations
Do not to split up JIDs into multiple input fields
Description
Rationale
Show user's room nickname and allow to change it
Description
Rationale
Use only TLS secured XMPP c2s connections
Description
Rationale
Do not to encode any semantics into the resource and don't specify a resource
Description
Instead of letting the user specify a resource or providing a pre-configured list of possible resource names (e.g. '/home', '/work', '/notebook') let the server generate a resource for your client (RFC 6120 7.6). 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
Resource names should not be guessable to prevent presence leaks (RFC 6120 13.10.2).
Show the type of a remote resource (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource
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 XEP-30 disco#info query results. So instead of having a resource like '/work-pc', the client should return
<identity category='client' type='pc' name='Work PC'/>
within the 'disco#info' results.
Rationale
Encoding semantic in the value of the resource is not recommend (see previous item).