| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
This is more explicit than taking the QXmppClient and asserting it has
an HttpUploadManager registered.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
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>
|