df88c51334
(Except for the actual streaming of receive-pack through XMPP, which can only run once we've gotten an appropriate uuid in a push initiation message.) Pushes are now only initiated when the initiation message comes from a known uuid. This allows multiple distinct repositories to use the same xmpp address. Note: This probably breaks initial push after xmpp pairing, because at that point we may not know about the paired uuid, and so reject the push from it. It won't break in simple cases, because the annex-uuid of the remote is checked. However, when there are multiple clients behind a single xmpp address, only uuid of the first is recorded in annex-uuid, and so any pushes from the others will be rejected (unless the first remote pushes their uuids to us beforehand. |
||
---|---|---|
.. | ||
Alert.hs | ||
BranchChange.hs | ||
Buddies.hs | ||
Changes.hs | ||
Commits.hs | ||
DaemonStatus.hs | ||
NamedThread.hs | ||
NetMessager.hs | ||
Pushes.hs | ||
ScanRemotes.hs | ||
ThreadedMonad.hs | ||
ThreadName.hs | ||
TransferQueue.hs | ||
TransferrerPool.hs | ||
TransferSlots.hs | ||
UrlRenderer.hs |