From 401ae5f6c45d42b0a411a5588ed355912ed2b6b7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 19:27:07 +0000 Subject: [PATCH] Added a comment --- ...mment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment diff --git a/doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment b/doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment new file mode 100644 index 0000000000..d72cad5b97 --- /dev/null +++ b/doc/forum/reliability__47__completeness_of_XMPP_updates/comment_1_e0f7aa48d54fc0564f41c3a569c723b7._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T19:27:07Z" + content=""" +Both clients have to be online at the same time for XMPP push to work. Once they're able to see each other, they'll sync up, even if they've diverged since the last sync. + +If you tend to only have one client or the other online, you should set up a git repo on a ssh server. Then clients will drop off their changes there, and the other one will check it when it comes online. (You don't really need to use XMPP at all in this case.) + +The most robust and fast combo is to use XMPP pairing, and also have a git repo on a ssh server. This way, when both clients are online, they'll use XMPP to instantly propagate changes, and when not the server is there to fall back to. +"""]]