On Fri, 26 May 2006, Christian W. Zuckschwerdt wrote:
URIs are not a concern of OpenOBEX. To users on the other hand it is not viable to present raw structs (i.e. obex_interface_t) least let them interact with those. So all programs using OpenOBEX (e.g. ObexFTP) would need to translate these both ways. Output some friendly results when discovering devices and let the user select from these (input ). I some cases this can be done transparently (e.g. with dialog options in guis). In the general case however a collapsed representation in a single character string is needed.
I think that friendly results are human-readable descriptions of the interfaces. For Bluetooth this could be device name and service name/class name. Ditto for USB. This is totally trivial to get from the interface structures, but impossible to get from URI strings. Also, if the program wants to only use a specific class of interfaces, you're forcing them to parse the URI into bits - going back to the raw structs.
This is also much more convenient for the language bindings in ObexFTP (I don't want to expose all the fussy details from FindInterface e.g.). There are six bindings in need of this already.
Again, you have to expose e.g. the USB or Bluetooth device name because the users of the programs that use the bindings want to know that. I don't see how that could be put into an URI, and providing separate API calls
makes the URI pointless.
To get to the point: this is something I want to do (in ObexFTP). And I hope to get some comments on a 'best URI scheme'.
Drop the idea, it's not worth it :) Alexander Homepage: http://www.sensi.org/~ak/ ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
