| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- EmpathyChannelFactory has been changed to EmpathyClientFactory and inherit
from TpAutomaticClientFactory.
- We now always use the _with_am variant of TpSimple* constructors
- We define our own factory as default.
- Replace empathy_get_account_for_connection() by tp_connection_get_account()
- The factory is passed to EmpathyTpChat and TpyCallChannel
- Use tp_simple_client_factory_ensure_account() instead of
tp_account_manager_ensure_account().
- Rely on the factory to prepare connection features.
This should ensure that all the TpProxy and TpContact objects created in
Empathy are shared and use EmpathyClientFactory.
https://bugzilla.gnome.org/show_bug.cgi?id=655799
|
|
|
|
| |
It's more convenient and safe than hardcoding them everywhere.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Handle errors that may arise when constructing the handler from the
factory.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|