From: Alex K. <ak...@se...> - 2005-07-22 18:46:03
|
On Fri, 22 Jul 2005, Christian W. Zuckschwerdt wrote: >> interface_name is a user-readable interface name - both Bluetooth and USB >> provide those. Capabilities is a bit field with interface capabilities >> (file transfer, syncml and so on). > > So those are for informational purpose only? For choosing the interface to connect to, yep. The actual ids, addresses and numbers are hidden in intf_ pointers, which the application doesn't need to access. >> So in this case [Nokia] the serial is the same for any phone. Which means >> there is no way to identify a USB device in a unique way between replugs. > > Like I said above. The lib should take care of the icky bits especially if we > can't choose the right device. Just select them in turn and probe for the > IMEI or something. But we can :) Devices and interfaces have readable names (e.g. "Nokia 7610" and "OBEX Object Push") and there's also capability information, so you can either present a list of those triplets to the user, or have an application choose the one it wants automatically. Where's the icky bit here? On the other hand, probing for IMEI, which has nothing to do with OBEX and may or may not be present, definitely doesn't belong in a generic obex protocol library. You should do it on a higher level, if you want to be ultra-sure you're connecting to the right device, but in most cases that's overkill, I think. Alexander Homepage: http://www.sensi.org/~ak/ |