aboutsummaryrefslogtreecommitdiff
path: root/doc/design/assistant/xmpp.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-11-09 14:34:06 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-11-09 14:34:06 -0400
commitdcaa93dd5aff1be6e085f689672c2ec35d5f49f1 (patch)
treece5cd2bae1b8625f5f43ec0af6d65d12db2ba5fd /doc/design/assistant/xmpp.mdwn
parentb8e1ac94f21661786dd1825418b9d1d512a6a878 (diff)
add canpush xmpp command
Diffstat (limited to 'doc/design/assistant/xmpp.mdwn')
-rw-r--r--doc/design/assistant/xmpp.mdwn11
1 files changed, 8 insertions, 3 deletions
diff --git a/doc/design/assistant/xmpp.mdwn b/doc/design/assistant/xmpp.mdwn
index b39d155e1..9ab8eabe6 100644
--- a/doc/design/assistant/xmpp.mdwn
+++ b/doc/design/assistant/xmpp.mdwn
@@ -56,13 +56,18 @@ For pairing, a chat message is sent, containing:
### git push over XMPP
+To indicate that we could push over XMPP, a chat message is sent,
+to the accounts associated with known XMPP remotes.
+
+ <git-annex xmlns='git-annex' canpush="" />
+
To request that a remote push to us, a chat message can be sent.
<git-annex xmlns='git-annex' pushrequest="uuid" />
-The push request is typically sent directed at the account associated
-with the remote, not to a specific client. So it can result in multiple
-responses.
+When replying to an xmpppush message, this is directed at the specific
+client that indicated it could push. But it can also be sent to
+the account associated with an XMPP remote to solicit pushes from all clients.
When a peer is ready to send a git push, it sends: