Am Montag 31 März 2008 schrieb Alex Kanavin: > 2008/3/31, Hendrik Sattler <[EMAIL PROTECTED]>: > > > 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? > > Well, in an OBEX session one side is a server, and another (the one > that issues the OBEX Connect command) is a client, this makes total > sense to me. There are many possible use cases for either variant: the > simplest is that you can push some files to your phone from your PC, > but you might want to push some files to your PC from your phone too. > Previously there was no way to know how the roles are assigned for a > given USB OBEX interface.
TCP, IrDA and bluetooth are working different, though, as you can listen for incoming connections. On USB, you have to inspect any newly attached device for that descriptor. Is this possible to get notifications with only libusb or is HAL needed? I mean something equal to listen() on a socket... > > > - 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. > > Why? If Bluetooth is already assigning numeric IDs to various OBEX > functionalities, it makes sense to reuse them in other transports, for > example, USB. E.g. because there are systems without bluetooth support but with a working libusb. Not sure but Solaris comes to my mind. Additionally, bluetooth support is optional when building. > > > - 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. > > Almost every modern mobile phone has USB OBEX, I was talking > specifically about this new descriptor. Samsung phones don't. Never seen a phone from SE that has this. Nokia does but not all models (known ones?). 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
