Christian, > That needs some thorough work. The connection id is available at the > application level (i.e. OpenFTP) while the continuation packet is > assembled at the library level (OpenOBEX) only. > I have noticed that, I'm working on it, I think It could break OpenObex compatibility, with other apps. I think I will have to modify the obex_object_t to add this. > Also this needs discussion if a quirk like that should get into the > library at all. > I don't think this should go into the official library, because of the simple reason that it breakes the specs. I will send the patch file, so that if any body else wants to use a device like this does not need to break his head like me.
> The section on connection identifiers (2.2.11 in IrOBEX 1.3) states that > only the first packet in each request _needs_ to contain the header. > The Get section (3.3.4) does not explicitly forbid new headers in > continuation get request. It just states an example where no new headers > are introduced. I think the same that you. I will send and email to CSR people about this. And tell them how they are breaking the specs. I think this must have a good reason, in the meaning that the device can have more than 1 connection alive while exchanging things over Obex. Regards, 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
