Hi Hendrik, >>>> I just found some patches on the linux usb mailing list about usb >>>> obex >>>> support (server side) from 2008-05-22. The obex implementation is >>>> in >>>> userspace, so I hope that'll go into libopenobex. Any comments? >>>> >>> No, those are patches for the linux kernel, I haven't looked at them >>> carefully, but I guess they'd provide an obex server device file, >>> which openobex can be connected to for implementing the protocol. >>> Openobex doesn't need to be modified for that. >>> >> >> it is for the OBEX USB gadget support. Non of them are final yet, but >> basically you get a character device where you than have to talk OBEX >> to. They are needed in case you wanna build a phone and offer FTP >> support over USB. >> > > Me already figured that from the patches ;-) > The question is if we are going to support that (when ready) natively. > By that I mean that the application author doesn't have to care how to > access the kernel to use that (accept configuring the kernel module to > enable obex), equal to libopenobex opening the bluetooth socket > correctly. Or is it up to the application author to open the right TTY > device and feed it to libopenobex?
the current idea goes more into the direction of using the FD transport. However adding a new transport for it would also be an option. This needs to figured out when the final patches go upstream. At the moment I would tell everybody to use the FD transport since especially if you work in code bases where you need async mainloop integration, that is the only way to do it properly. Regards Marcel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
