Christian,
Thanks for the reply, you taken your time to came out with a conclusion. 
I like that :)
> 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."
>   
Yes, I know that, but 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.

> 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.
>   
I'm sorry to tell that fixing AIRcable is impossible. You mean that 
instead of sending the hole data package to OpenObex I control data flow 
from ObexFTP? I was working on fixing a Java Obex implementation, but I 
have no problem in coming back to OpenObex :).
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 :)

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

Reply via email to