Manuel, Manuel Naranjo schrieb: > there is a problem, which is not only applied to > AIRcable devices. A lot of devices that use CSR chips can have the same > kind of problem. I'm sorry to tell that fixing AIRcable is impossible. > I thought so. And if we don't compromise the openobex code we can include a workaround.
> instead of sending the hole data package to OpenObex I control data flow > from ObexFTP? That would be too much effort. At present it looks like this: the PUT is broken down to packets. The first one includes all the headers (presumably) and some part of the body. A CONTINUE packet is send back. The next body part is send (without non-body headers). If the CONTINUE packet includes a connection id header we can copy it to the next packet each time. Can you check if the response packets are 0x90 0x00 0x03 or 0x90 0x00 0x08 0xCB ... > If you want I can send you an AIRcable device, so you can test too. Let > me know, the CEO of the company has let me give you some of those devices :) > nice. Giving away gadgets gets the attention of developers, always ;) regards, Christian ------------------------------------------------------------------------- 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
