Manuel, I did some more research with this issue and came to this conclusion: When an OBEX request is split into a number of packets headers are not to be repeated. Headers are defined on the level of requests.
Section 3.6.1 reads "This type of multiplexing only requires one OBEX parser because the multiplexing occurs above the parser." That way the state information inside the openobex parser should not include any connection id. Also section 2.1 reads "The behavior by the recipient of multiple non-Body headers is not defined by the protocol." And then 2.2.11 explicitly says "Only the first packet in the request needs to contain the Connection Id header. As a result, only one request can be processed at a time." If the AirCable device can't be fixed we can perhaps come up with some workaround. I disapprove of connection id handling inside openobex though. One way might be to re-send a connection id header if it is received with the RSP_CONTINUE (0x90) packet. I.e. extend the PUT handling to copy over a connection id header. regards, Christian Manuel Naranjo schrieb: > I have corrected some > things, the GET is working all right for me, but the PUT is not working > at all. >> So obexftp needs to revisit its support for Connection IDs, following >> OBEX13.pdf sections 2.2.11 Connection Id, and 4.6 Directed Operations >> and Connections ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
