Re: [RFC obexd 00/10] Major API changes in obex-client

[Mikel Astiz <mikel.astiz@bmw-carit.de>]

Hi Luiz,

> I will be doing some cleanups before we integrate this code, some are
> based on your mega patch that  you have sent (actually it never made
> to the list due to its size), but I would like to separate the
> transport code to modules e.g. bluetooth like we did for obexd so the
> session just call e.g. .connect/.disconnect and the driver takes care
> of the transport details such as requesting a session and discovering
> records, this should simplify quite a lot session.c

I agree it would be convenient to have a simplified session.c. Right now 
there is definitely too much in there.

I am about to finish a split of the mega-patch you mention, trying to 
separate the internal changes from the dbus-related changes, as we 
discussed. You may want to wait until I send this new proposal.

> The only problem is how we gonna interpret the address, by default it
> should be Bluetooth but perhaps we should support urls for other
> transport e.g. usb://, how about that?

Sounds fine to me.

Cheers,
Mikel