|
171
|
1 #summary XEP-0198: Reliability and fast reconnects for XMPP |
|
|
2 #labels Stage-Beta |
|
|
3 |
|
|
4 = Introduction = |
|
|
5 |
|
|
6 By default XMPP is as reliable as your network is. Unfortunately in some cases that is not very reliable - in some network conditions disconnects can be frequent and message loss can occur. |
|
|
7 |
|
|
8 To overcome this, XMPP has an optional extension (XEP-0198: Stream Management) which, when supported by both the client and server, can allow a client to resume a disconnected session, and prevent message loss. |
|
|
9 |
|
|
10 = Details = |
|
|
11 |
|
|
12 When using XEP-0198 both the client and the server keep a queue of the most recently sent stanzas - this is cleared when the other end acknowledges they have received the stanzas. If the client disconnects, instead of marking the user offline the server pretends the client is still online for a short (configurable) period of time. If the client reconnects within this period, any stanzas in the queue that the client did not receive are re-sent. |
|
|
13 |
|
|
14 If the client fails to reconnect before the timeout then it is marked offline as normal, and any stanzas in the queue are returned to the sender as a "recipient-unavailable" error. |
|
|
15 |
|
|
16 = Configuration = |
|
|
17 |
|
|
18 || *Option* || *Default* || *Description* || |
|
|
19 || smacks_hibernation_time || 300 (5 minutes) || The number of seconds a disconnected session should stay alive for (to allow reconnect) || |
|
|
20 |
|
|
21 = Compatibility = |
|
|
22 ||0.8||Works|| |
|
|
23 |
|
|
24 = TODO = |
|
|
25 * Doesn't work very well with multiple virtual hosts yet (just a plugin implementation detail). |
|
|
26 * Related to the above issue - reload/unload of this module may not work very well. |
