aboutsummaryrefslogtreecommitdiff
path: root/doc/design/assistant/xmpp.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-07-08 12:34:09 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-07-08 12:34:09 -0400
commit8ca8cef8324c736d20c6b3a44b5c8554b855c128 (patch)
tree6f91e2e592c2a88bbb5889875fe0606682219316 /doc/design/assistant/xmpp.mdwn
parent935869a41a8a2769fe68561c12723d20eccc7b97 (diff)
TCP over XMPP
Diffstat (limited to 'doc/design/assistant/xmpp.mdwn')
-rw-r--r--doc/design/assistant/xmpp.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/design/assistant/xmpp.mdwn b/doc/design/assistant/xmpp.mdwn
index 627a2229a..5e5efbaa5 100644
--- a/doc/design/assistant/xmpp.mdwn
+++ b/doc/design/assistant/xmpp.mdwn
@@ -9,6 +9,10 @@ who share a repository, that is stored in the [[cloud]].
See <http://git-annex.branchable.com/design/assistant/blog/day_114__xmpp/#comment-aaba579f92cb452caf26ac53071a6788>
* Support registering with XMPP provider from within the webapp,
as clients like pidgin are able to do.
+* At least some XMPP servers are lossy (does XMPP guarantee delivery)?
+ I have seen a log where a push's packet 1 and 3 arrived, but 2 did not.
+ To deal with this, need at least a 1 packet buffer and ACK or resend
+ request implemented over top of XMPP. Essentially, TCP over XMPP. :(
* Add an encryption layer that does not rely on trusting the XMPP server's
security (currently it's encrypted only to the server, not end-to-end).
There are a few options for how to generate the key for eg,