assistant: Get back in sync with XMPP remotes after network reconnection, and on startup.
Make manualPull send push requests over XMPP. When reconnecting with remotes, those that are XMPP remotes cannot immediately be pulled from and scanned, so instead maintain a set of (probably) desynced remotes, and put XMPP remotes on it. (This set could be used in other ways later, if we can detect we're out of sync with other types of remotes.) The merger handles detecting when a XMPP push is received from a desynced remote, and triggers a scan then, if they have in fact diverged. This has one known bug: A single XMPP remote can have multiple clients behind it. When this happens, only the UUID of one client is recorded as the UUID of the XMPP remote. Pushes from the other XMPP clients will not trigger a scan. If the client whose UUID is expected responds to the push request, it'll work, but when that client is offline, we're SOL.
This commit is contained in:
parent
dbcf26e7bc
commit
c23ea9e311
7 changed files with 107 additions and 33 deletions
|
@ -9,8 +9,6 @@ who share a repository, that is stored in the [[cloud]].
|
|||
* Do git-annex clients sharing an account with regular clients cause confusing
|
||||
things to happen?
|
||||
See <http://git-annex.branchable.com/design/assistant/blog/day_114__xmpp/#comment-aaba579f92cb452caf26ac53071a6788>
|
||||
* Assistant.Sync.manualPull doesn't handle XMPP remotes yet.
|
||||
This is needed to handle getting back in sync after reconnection.
|
||||
* Support use of a single XMPP account with several separate and
|
||||
independant git-annex repos. This probably works for the simple
|
||||
push notification use of XMPP, since unknown UUIDs will just be ignored.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue