Am Montag 31 März 2008 schrieb Alex Kanavin: > the USB IF has published a new version of the CDC specification, and > it has an updated version of the USB OBEX interface standard. The main > new thing is the introduction of the optional "OBEX Service > Identification Functional Descriptor" which contains the following > information: > > - whether the interface is an OBEX server or a client
Huh? How is that going to work? Or ask in another way: what is this supposed to be good for? > - a 16 byte UUID describing the service that this interface > implements. The UUID values are same as Bluetooth: Still, this should be implemented independently of the bluetooth interface. > - a version of the provided service > > I'm not aware of any devices that implement this, but I'll write a > patch that makes this information available to applications anyway. Great. I've yet want to see a device that has USB OBEX. HS ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
