Christian W. Zuckschwerdt wrote: > Hendrik Sattler schrieb: > >> The examples in the spec are just not useful enough, lazy writers: one >> request >> seems to be all packets associated with a specific command, e.g. a put. >> So I revert my opinion but I can understand developers that get confused by >> this wording :-/ >> >> > > That's exactly the problem with the CSR implementation. > > If you think and read really hard you can conclude where the distinction > between requests and packets is. And that only requests are supposed to > carry the connection id header. (2.2.11 "Only the first packet in the > request"... gives a clue to that) > > If this is a correct deduction at all, it is far from obvious. >
We are against of a bad designed spec :). Obviously this can reach to a lot of different interpretations. But if CSR, and Widcomm understood the same thing, for something must be. Remeber something, unfortunately we are not the one's who build the hardware. so we are not the ones who define the standard. One thing is the written standard, and another completely different is the way it works (the real standard). There is an spec for testing also, it can be reach here: https://obex4j.dev.java.net/files/documents/2519/9270/OBEX_Test_Spec_V1p0p1.pdf, has anyone tested OpenObex? Maybe we should grab this document and see if open obex is compatible with this testing. Another thing, I can't remeber which were the CFLAGS that I needed to send Open Obex and ObexFTP to enable debug. Cheers, Manuel ------------------------------------------------------------------------- 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
