2009/1/29 Bastien Nocera <had...@hadess.net>:
>> It is also possible to just fork USB interface discovery code from
>> openobex to ods. That way we wouldn't break openobex API and ods
>> wouldn't have to depend on very recent openobex version (furthermore,
>> nobody knows when it would be released anyway).
>
> That would be a lot of cut'n'paste code that would need to replicate the
> whole obex_interface_t structure for USB. This doesn't seem like a good
> idea to me from a maintenance point of view.
>
> Then again, it's about 500 lines of code (with the necessary changes,
> and headers), and would add a direct libusb dependency on
> obex-data-server.
>
> I'd like to hear from the maintainers before we get forward with that
> plan.
You would need to provide a correct
/** Internal information for the transport layer in the library */
struct obex_usb_intf_transport_t *intf;
pointer to a structure that's internal to openobex. How would you do
that? Doesn't seem like a good idea to me either.
--
Alexander
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Openobex-users mailing list
Openobex-users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/openobex-users
