summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://edheil.wordpress.com/ <http://edheil.wordpress.com/@web>2013-07-16 19:05:49 +0000
committerGravatar admin <admin@branchable.com>2013-07-16 19:05:49 +0000
commit74b2b0ac03dbc8827efa06ae44989be28b3fcabe (patch)
tree0ae4022a2cf940764d8ccfb135d4c1290252e058
parent79e4074892cd0822c364cc2ea36af82e68a8a845 (diff)
-rw-r--r--doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn b/doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn
new file mode 100644
index 000000000..fc558aad6
--- /dev/null
+++ b/doc/forum/reliability__47__completeness_of_XMPP_updates.mdwn
@@ -0,0 +1,7 @@
+This falls into the category of "noob questions" I think.
+
+The one piece of the git-annex assistant puzzle I've never messed with is XMPP pairing. I'm wondering how well a pair of repos can keep in sync with each other if their only connection is via XMPP. Will things go badly if changes are made to one while the other is offline? Do messages get queued up to deliver when they're both online? (Or do they get queued on the server side so they can be delivered even if one of them is online, makes changes, then goes offline, and the other one comes online later?)
+
+If some xmpp messages don't go through for whatever reason, will the remotes be able to "catch up" with each other later on and make up for lost time?
+
+Just hoping for a general sense of the limitations of XMPP pairing. TIA.