Fork of the QXmpp library. https://gitea.privatedns.org/xavi/qxmpp/atom?h=fork 2022-10-02T21:01:13+00:00 2022-10-02T21:01:13+00:00 Linus Jahn lnj@kaidan.im 2022-10-02T02:06:31+00:00 urn:sha1:a58f415f064a34136545da3333f96d2e83b23b29 This is more explicit than taking the QXmppClient and asserting it has an HttpUploadManager registered. 2022-10-02T21:01:13+00:00 Linus Jahn lnj@kaidan.im 2022-10-02T00:45:09+00:00 urn:sha1:b871f6d3557c20fc7d1456e5080c33ea90795c84 Previously all the providers had to subclass the QXmppUpload/Download. It should be much easier to do additional tasks (e.g. hashing after downloading) now because the manager (and not the provider) decides when to emit the finished signal. Making the encrypted source provider able to handle arbitrary unencrypted sources should be possible too. 2022-09-29T21:46:36+00:00 Jonah Brüchert jbb@kaidan.im 2022-09-09T21:15:10+00:00 urn:sha1:68f167995e7ba71a6f2e556a7a0eab3d234e2d1a This adds a file sharing manager that is capable of using multiple back ends. Currently implemented are a normal HTTP File Upload backend and an encrypted HTTP File Upload. Jingle File Transfer could be implemented later. Co-authored-by: Linus Jahn <lnj@kaidan.im>