Difference between revisions of "XMPP IM Client Design Guidelines"

XMPP IM Client Design Guidelines (view source)

220 bytes added , 13:57, 4 September 2015

168

edits

@@ Line 33: / Line 33: @@
 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 (RFC 6120 7.6)]. Servers are required to support this. 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.
-Store the resource you obtained from the server on the first connection, and re-use that on later connections. That way, a properly-configured server will close your old session if it still was deemed active by it.
+Ideally you also store the resource you obtained from the server on the first connection, and re-use that on later connections. That way, a properly-configured server will close your old session if it still was deemed active by it. But make sure to handle [http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions-conflict 'conflict' stream errors] in case the server terminates the '''new''' session with a 'conflict' stream error.
 === Rationale ===