This commit is contained in:
Joey Hess 2013-03-06 21:49:17 -04:00
parent c16adc25c4
commit 15ef899b12
2 changed files with 4 additions and 0 deletions

View file

@ -115,3 +115,5 @@ I'm not 100% sure this sort of multiway synching is supposed to work, so maybe t
This issue also made me wonder about how one would go about syncing multiple unrelated annexes via XMPP. Would you need a different gmail account for each? Maybe there is a trick similar to the email local+foo@ thing? This issue also made me wonder about how one would go about syncing multiple unrelated annexes via XMPP. Would you need a different gmail account for each? Maybe there is a trick similar to the email local+foo@ thing?
> [[done]], turned out I left XMPP git push working,
> but had not done all the stuff around it to get reliable syncing. Now have. --[[Joey]]

View file

@ -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'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. I think it explains everything in this bug report, hopefully.
(All XMPP nodes sync with all other nodes, BTW.)
"""]] """]]