From: Hendrik S. <po...@he...> - 2005-02-25 19:19:51
|
Am Freitag, 25. Februar 2005 18:18 schrieb Alex Kanavin: > On Fri, 25 Feb 2005, Hendrik Sattler wrote: > > This does not make it any less complex because you need to setup a > > special struct for every type. > > Yes, but if you're writing libraries for specific application-level > protocols which work over obex (there's more than just file transfer), you > can make them completely transport-independent that way. The application > sets up a structure and passes it all the way down to the openobex > library. It would be nice to make obexftp library work like that, wouldn't > it? If I think about it, I doubt that it would reduce the amount of work for th= e=20 application (it has to build a proper struct for each type it wants to=20 support and provide an interface to the user to enter them). The only effec= t=20 would be a more stable API. > > However: I know that OBEX was defined for IP, IrDA and Bluetooth. But > > what is "Fd" (file descriptor?) > > Yep. Hmm, cannot quite imagine this but nevermind. HS =2D-=20 Mein GPG-Key ist auf meiner Homepage verf=FCgbar: http://www.hendrik-sattle= r.de oder =FCber pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org |