aboutsummaryrefslogtreecommitdiff
path: root/doc/design/assistant/xmpp.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-03-07 11:09:21 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-03-07 11:09:21 -0400
commit75578197b885be42e8f3a8ddaf1f9f3f3be7726a (patch)
tree162c7ad7b8a003a8b6d9984f437311837b123379 /doc/design/assistant/xmpp.mdwn
parent44bd60408469b492a223580c23eb08d2cbb6d62f (diff)
note
Diffstat (limited to 'doc/design/assistant/xmpp.mdwn')
-rw-r--r--doc/design/assistant/xmpp.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/design/assistant/xmpp.mdwn b/doc/design/assistant/xmpp.mdwn
index fed79527e..4b317fb9a 100644
--- a/doc/design/assistant/xmpp.mdwn
+++ b/doc/design/assistant/xmpp.mdwn
@@ -14,6 +14,11 @@ who share a repository, that is stored in the [[cloud]].
push notification use of XMPP, since unknown UUIDs will just be ignored.
But XMPP pairing and the pushes over XMPP assume that anyone you're
paired with is intending to sync to your repository.
+* Disconnect network, make change, stop assistant, reconnect network,
+ start assistant. Change is not propigated. Seems nothing handles
+ calling reconnectRemotes on startup. (If the change gets committed during
+ startup, it does get synced out, by other means.) This is probably not
+ xmpp specific really.
## design goals