2009/1/29 Bastien Nocera <had...@hadess.net>: > And a few calls to ods_usbobex_free_interfaces() were missing as well.
OBEX_Cleanup does the same thing though. >> > I've changed the code to not use the same structures as openobex does >> > internally, to avoid such confusion. >> >> Aah, now I see how this works. I'd use Bus/Device/Interface integers >> in the D-Bus API instead of Path though, that's what openobex is going >> to provide. > > It's a path triplet. Tadas can call it ID, or something else. I just don't see why this is better than three separate numbers. >> Now it's up to Tadas if he wants to include all of this, or wait until >> the same thing is available directly from openobex. > > I don't mind either way. But I have the feeling that Tadas will be > quicker at bringing this into a release than openobex would be. Feel > free to prove me wrong though :) Actually I agree with you - Marcel is unresponsive lately, and if he's too busy with bluez or whatever, he should hand openobex over to Hendrik or Christian if either agrees. IMO :) -- 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
