2009/1/29 Bastien Nocera <had...@hadess.net>:
> Using the same code as openobex for the device discovery, and fixing a
> few memleaks in the process.
>
> Patch for obex-data-server attached.

Quite a hack:

+/* Information about a USB OBEX interface present on the system */
+struct obex_usb_intf_transport_t {

You copied an internal structure from openobex to ods, how are you
going to keep it in sync? It's going to change, and I can't make any
promises about keeping it stable. Also, the external structure still
needs the path member, how do you solve this without patching
openobex?

-- 
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

Reply via email to