summaryrefslogtreecommitdiff
path: root/Assistant/XMPP.hs
Commit message (Collapse)AuthorAge
* more refactoringGravatar Joey Hess2012-11-10
|
* more nice refactoringGravatar Joey Hess2012-11-10
|
* better data types allowed marvelous refactoringGravatar Joey Hess2012-11-10
|
* separate data type for push stagesGravatar Joey Hess2012-11-10
| | | | This improves type safety.
* refactorGravatar Joey Hess2012-11-10
|
* use a lookup table for speedGravatar Joey Hess2012-11-10
|
* fix murderous typoGravatar Joey Hess2012-11-09
|
* add canpush xmpp commandGravatar Joey Hess2012-11-09
|
* hooked up XMPP git push send/receive (but not yet control flow)Gravatar Joey Hess2012-11-08
|
* data types and xml generation/parsing for xmpp pushGravatar Joey Hess2012-11-07
|
* better git-annex tag handlingGravatar Joey Hess2012-11-07
| | | | Allow the tag to contain a value. Better extraction of the attribute value.
* switch to silent chat messages for XMPP pairingGravatar Joey Hess2012-11-05
| | | | | Along the way, significantly cleaned up Assistant.XMPP, and made XMPP message decoding more efficient.
* workaround for Google Talk's insane handling of self-directed presenceGravatar Joey Hess2012-11-03
| | | | | | | | Maybe the spec allows it, but broadcasting self-directed presence info to all buddies is just insane. I had to bring back the IQ messages for self-pairing, while still using directed presence for other pairing. Ugly.
* avoid repeated pairing alertsGravatar Joey Hess2012-11-03
|
* switch to directed presence for pair requestsGravatar Joey Hess2012-11-03
| | | | | | | | | | | | | | | | | | | | | Testing between Google Talk and prosody, the directed IQ messages were not received. Google Talk probably only relays them between clients using the same account. I first tried even more directed presence, with each client JID being sent a separate presence, but that didn't work on Google Talk, particularly it was ignored when one client sent it to another client using the same account. So, presence directed at the user@host of the client to pair with. Tested working between Google Talk and prosody (in both directions), as well as between two clients with the same account on Google Talk, and two clients with the same account on prosody. Only problem with this form of directed presence is that if I also use it for git pushes, more clients than are interested in a push's data will receive it. So I may need some better approach, or a hybrid between directed IQ and directed presence.
* update xmpp protocolGravatar Joey Hess2012-11-03
| | | | | | | | | Amusingly, I am not really using xmpp ping for pairing. I forgot to put in the ping tag! And when I did, it stopped working, on Google Talk. Seems it handles client to client pings, at least using the same JID, without actually sending them to the end client. My mistake avoided this, and seems to work, so I've left it as-is for now, with just the git-annex tag in an IQ message. Also tested on prosody.
* XMPP pair requests are now received, and an alert displayedGravatar Joey Hess2012-11-03
|
* XMPP pairing notifications are now sentGravatar Joey Hess2012-11-03
| | | | Rest of pairing process still to do.
* send a presence query when the buddy list is displayedGravatar Joey Hess2012-11-03
| | | | | This ensures that clients that have not sent presence in a while will show up in the list.
* refactor XMPP clientGravatar Joey Hess2012-11-03
|
* xmpp buddy list trackingGravatar Joey Hess2012-11-02
|
* where indentationGravatar Joey Hess2012-10-31
|
* send git-annex tag in initial presenceGravatar Joey Hess2012-10-28
| | | | Will be used for finding other git-annex clients for pairing
* reconnect XMPP when NetWatcher notices a changeGravatar Joey Hess2012-10-27
|
* gnutls segfault fixedGravatar Joey Hess2012-10-26
| | | | | | | | Adjust build deps to ensure that only a fixed version of the library will be used. Also, removed the bound thread stuff, which I now think was (probably) a red herring.
* split out xmpp utilitiesGravatar Joey Hess2012-10-26