From 4581ce68361c0d318c325af99a961b67de01e958 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 6 Mar 2013 21:49:17 -0400 Subject: fixed --- .../comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment | 2 ++ 1 file changed, 2 insertions(+) (limited to 'doc/bugs/three_way_sync_via_S3_and_Jabber') diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment index 8389641a8..c611b7d6e 100644 --- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment +++ b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment @@ -7,4 +7,6 @@ I've been revisiting the XMPP stuff this week, and today I fixed at least 3 problems that would keep XMPP sync from happening reliably. This would affect machines that are using XMPP and are sometimes disconnected from the net (or suspended). Nothing caused a sync to happen when restarting the assistant, or resuming from a network disconnection. This could result in both files not showing up, and file contents not being transferred, depending on the case hit. I think it explains everything in this bug report, hopefully. + +(All XMPP nodes sync with all other nodes, BTW.) """]] -- cgit v1.2.3