On Thu, 28 Oct 2010, Maksim Yevmenkin wrote: > > One thing that I can't check, what would happen if the "obexapp client GET > > -> remote" session get response did contain a Connection ID already, > > would we send it twice? > > i'm not sure... i'm tempted to say no because header are parsed, i.e. > we effectively move headers to another list (that is why we need > reparse call). however, this is something that openobex library does > internally, so, we need to test it.
I thought about this and maybe it is a little clearer .. the object that is handed to the stream read/write functions is in fact the base GET/PUT command that openobex thinks we should be sending.. so it should be up to us to add any Connection ID headers since openobex doesn't know about them > would be really nice to try it again apple mac os x. those guys usually > do things according to standards :) obexapp works against Mac OS X 10.6 (see 2.5Mb log of get and put with connections from either side at www.netbsd.org/~plunky/obexapp-macos.txt) I also tried my wm6 phone against it and it works fine too but I don't have a packet sniffer on the mac iain _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[email protected]"
