| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Remove the use_hash construct arg and property from EmpathyFTHandler and
make it clear in the docs how clients are supposed to know whether we
are hashing or not.
Also, port EmpathyFTFactory to the new API
|
| | |
|
| |
|
|
|
| |
Add use_hash params for incoming transfers to the FT Factory and
Handler, so that we will use them to check hash for received files.
|
| |
|
|
| |
Update the factory API to make hashing request optional.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Now, a client should have to do the following, in order to receive a file transfer:
- let the EmpathyFTFactory claim the EmpathyDispatchOperation
- the factory will emit "new-incoming-transfer" when the handler is filled with
the relevant properties
- now you can choose a destination file, and then you should call _set_destination
on EmpathyFTFactory passing the handler.
- the factory will emit "new-ft-handler" as you're now ready to start the actual
transfer.
|
| | |
|
| | |
|
| | |
|
| |
|
