Hi Hendrik, On Wed, Jun 15, 2011, Hendrik Sattler wrote: > Zitat von Johan Hedberg <johan.hedb...@gmail.com>: > >And as Marcel correctly pointed out on linux-bluetooth OBEX over L2CAP > >actually uses enhanced L2CAP and will therefore have SOCK_STREAM as the > >socket type. So no issue here. > > My posted patches also use SOCK_SEQPACKET. There is nothing > essentially wrong with that. But I could use SOCK_STREAM, too. It > might make the code simpler. However, does anybody has a clue about > the way this is going to be handled on FreeBSD/NetBSD? Will they > actually ever support ERTM? > > However, my patches also use L2CAP socket options that are using > functions named "xxxx_old" in linux kernel for setting IMTU and ERTM > mode. Is there another suggested way of setting ERTM mode? Can > someone ask Marcel? I don't see another way in the current code of > Linus' kernel tree.
Let's just see how the current thread on linux-bluetooth evolves (I hope you're subscribed there by now). Based on the messages from Tim and Piotr it seems that this SOCK_STREAM convention might need some reconsideration. > Maybe Obex-over-L2CAP is just not ready, yet? Functionally it should be perfectly ready. After all, it's already successfully being used for HDP in BlueZ. But as we've now seen the API might need rethinking. Johan ------------------------------------------------------------------------------ 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