Zitat von "Hendrik Sattler" <p...@hendrik-sattler.de>: > Zitat von "hui li" <nami.li1...@gmail.com>: > >> 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. > > Same for USB, so what? Just put your whole packet into rx_msg on the > first read! That's exactly what USB does!
Ok, if your transport is a custom transport, this may be difficult. Either you have to have to use OBEX_CustomDataFeed() or we have to resize the rx_msg buffer in the read() method of the custom transport hook like done for USB. The last argument for a read() function just indicates how much bytes we need to go on, not how much you are allowed to put into the buffer. HS ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
