| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
The signal parameter does not work with immediately finishing
uploads/downloads (i.e. when an error happened while starting). The user
can't handle the result in that case.
|
| | |
|
| |
|
|
| |
Can only handle QFiles currently.
|
| |
|
|
|
| |
However it is still limited by the sources supported by
EncryptedHttpFileSource.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
The file sharing manager now generates SHA-256+SHA3-256 with Qt 5 and
SHA-256+BLAKE2b256 with Qt 6.
|
| | |
|
|
|
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>
|