Proposal for major API changes in obex-client

Hi all,

I would like to propose some changes in obex-client's D-Bus API, 
refactoring parts of the existing API and rewriting others.

The main goals would be the following:

     - Higher level representation of devices and sessions, following 
the BlueZ style.
     - OPP operations wrapped into a specific session type, just like 
the rest.
     - Transfer objects are created always, making the API more orthogonal.
     - Content of the pulled files is written to a file, avoiding dbus 
overhead.
     - Removal of agent, since all requests are locally initiated.
     - Transfer progress reported using unicast signals to transfer 
initiator.

Given that the diff would be quite unreadable, I attach the modified 
'client-api.txt' document.

Please consider this as a first draft, open for discussion. I hope at 
least some of these points are valid.

Cheers,
Mikel