Zitat von Hendrik Sattler <p...@hendrik-sattler.de>: > Zitat von Johan Hedberg <johan.hedb...@gmail.com>: >> Hi Hendrik, >> >> On Wed, Jun 15, 2011, Hendrik Sattler wrote: >>> @Johan: Looking at [1], what are the reasons that osso-gwobex is >>> using FdOBEX instead of BtOBEX? >> >> libopenobex is intended to be LGPL, but linking it with libbluetooth >> makes it effectively GPL. Because of this Maemo has never shipped a >> libopenobex with the Bluetooth specific parts compiled in and neither >> does MeeGo (AFAIK; I haven't actually verified this). > > libopenobex does not link with libbluetooth. Only the example > applications do. > >> Additionally, handling Bluetooth sockets within the application and >> passing them to FdOBEX is quite simple, and we even have GLib wrappers >> like BtIO which make using FdOBEX much more consistent with the rest of >> the BlueZ & obexd code bases than BtOBEX would ever do. > > Ok. Then you need (a possible updated) patch to use L2CAP, don't you?
I must correct myself, you don't. The FdOBEX code will read the full packet without any change, even for SEQPACKET sockets. @Nami: Your patch is not needed, at least not for latest openobex. Try it. HS ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
