- HTTP upload implementation
- if the upload link is HTTPS, certificate is checked (can be disabled on demand)
- file can be uploaded directly, or a put/get slot can be requested without actual upload.
The later is mainly useful for distant frontends like Libervia
- upload plugin manage different upload methods, in a similar way as file plugin
- download url is sent in progressFinished metadata on successful upload
- actions transport-replace, transport-accept and transport-reject are now handled
- transportReplace can be used from an other plugin
- new A_DESTROY action, used to clean a transport before its replacement
- progressStarted have a new metadata parameter, useful to know the kind of progression, direction, etc. Check bridge doc
- progressGetAllMetadata can be used to retrieve this data and discover on currently running progressions
- progressFinished also have a new metadata parameter, used to e.g. indicate that hash is checked
- core: fixed progressGetAll
- file, XEP-0234: implemented the API modifications, hash is returned on progressFinished
- file: SatFile.checkSize allows to check size independently of close (be sure that all the data have been transfered though)
- getClient now raise a NotFound error if client is not available
- errors ConnectedProfileError, NotConnectedProfileError anf ProfileKeyUnknownError renamed for consistency (all profile error must prefixed by Profile)
- launchAction fixed, the case where client is not available is handled
- kept actions are actuall1y removed on launchAction
- added a new mechanism to keep actions until they are answered (or timeout-ed)
- keep_id must be explicitly used on actionNew
- actionsGet is used to retrive these actions
- the mechanism is used in deferXMLUI
- parseHashElt do what it says
- calculateHashElt can calculate a whole hash in a non-blocking way
- or getHasher can be used for progressive hashing
- getBestPeerAlgo return the best available hashing algorithm of an entity
- progress use new API, and signals to monitor progression and avoid use of progressGet before progress is actually started
- progress behaviour on event is managed by callbacks which are Jp attributes
- progress with unknown or 0 size don't show the progress bar
- better handling of errors
- CommandAnswering is update to manage actions instead of the deprecated askConfirmation
- managed actions use callback easy to associate with an action type.
- file command is updated to manage these changes and the recent changes in backend behaviour
- verbosity is used to display more or less message when sending/receiving a file
- destination path can be specified in file receive
- file receive doesn't stop yet, still need some work in the backend
