Hi folks, 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 - a 16 byte UUID describing the service that this interface implements. The UUID values are same as Bluetooth: "An OBEX USB Service UUID takes the form of a 128-bit value (see [LEACH1998]), uniquely identifying a particular OBEX service. Bluetooth service class constants are usually defined in a 16 bit UUID format. These 16 bit UUIDs are directly transformable into the usual 128 bit UUID format, following rules set down in the Bluetooth core specification. When these service class constants are utilized in bOBEXServiceUUID, they shall be expanded to their full 128 bit UUID format" - 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. -- Alexander ------------------------------------------------------------------------- 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
