Sorry, is yor patch still use obex_data_indication() and obex_transport_read() to read socket data? It seems that your modified custom_read() function isn`t called by the two functions. Or you use OBEX_CustomDataFeed() to read data? Thanks.
2010/11/13, Hendrik Sattler <p...@hendrik-sattler.de>: > Am Freitag 12 November 2010, 07:57:17 schrieb hui li: >> Currently when openobex calls obex_data_indication() to read socket >> data, it first calls obex_transport_read() to read first 3 data to >> decide message length, then calls obex_transport_read() again to read >> remaining data. But when we run obex over l2cap, you can find the >> second obex_transport_read() return zero. > [...] >> actual = obex_transport_read(self, MAX_BUFF_SIZE); > [...] > > Please check > http://www.gitorious.org/openobex/mainline/commit/be1b3863d52b7daaa670245d8a88e8ccdacf7334 > > Does that help you? It resizes the available buffer to have RX MTU bytes (no > packet from the client should be larger than that) and you can fill that > with > your data. The RX MTU can be set by your own code. > Still, a proper solution was always possible using OBEX_CustomDataFeed() or > by > buffering the data in your own 64k buffer. > You cannot call obex_transport_read() like proposed by you when usually > using > blocking sockets or file descriptors. > > HS > ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
