Zitat von "hui li" <nami.li1...@gmail.com>: > OBEX_MT_SEQPACKET and OBEX_MT_STREAM indicate different socket types > ,corresponding to SOCK_SEQPACKET and SOCK_STREAM. If obex is over > l2cap, we may would like to use SOCK_SEQPACKET type and > obex_data_indication() function may need to how to parse incoming > data.
Actually not. The transport reads data from somewhere. How that is done is completely up to the transport. Note that you based that patch on 8 month old code and much happened since then. Also note that the transport's read() function can return more bytes than requested, e.g. USB support always does that (it always reads a full packet) and custom transports always did. This is not a problem. Where exactly is OBEX-over-L2CAP-without-RFCOMM specified? The bluetooth specs that I've seen so far always said that OBEX is bound to RFCOMM. HS ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
