Am Montag 16 Oktober 2006 17:33 schrieb Christian W. Zuckschwerdt: > 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."
I am afraid that you are wrong here. Take a look at chapter 4.6 for directed connections. The state "Once a directed connection is established, the client can direct operations to the same service by simply including the Connection Id header in each request." "request" is the thing to think about here. In the examples in chapter 7, a request is also each body part and the end-of-body part. The multiplex operation cited by you just give multiplex on a lower level to be really concurrent. The form of multiplex above only allow one request after the other for each connection id _or_ the standard inbox. But if you do not include the connection id in every request, the request will go to the inbox. The inbox didn't receive the connect request, though, so this will fail or even worse corrupt another stream. HS ------------------------------------------------------------------------- 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
