obexapp get failure

[Maksim Yevmenkin]

On Tue, Oct 26, 2010 at 1:19 AM, Iain Hibbert <plunky at rya-online.net> wrote:
> On Mon, 25 Oct 2010, Maksim Yevmenkin wrote:
>
>> i'm convinced that there is a bug in obexapp (or, less likely,
>> openobex library). it appears that "connection id" header is intended
>> for multiplexing of several data streams. its pretty much analog of
>> http "host" header.
>
> for what its worth, obexftp-0.20 exhibits the exact same behaviour as
> obexapp.

well, sadly, i'm not surprised. its based on openobex as well.

> (there are later versions but I can't be bothered to try and build them at
> this time, I have submitted patches to clean up Bluetooth support on *BSD
> over a year ago but the git repository shows no related activity)

not sure if obexftp still being actively used. last time i checked
there was a bunch of bluetooth-obex related code in gnome/kde etc. i
dont keep track of it - things change too fast in linux land :)

>> i think its clear what "connection id" header must be present on all
>> requests from the client, including continue-GET request. what is not
>> entirely clear if the server responses should also contain "connection
>> id" header. i think they should as well. clearly, wm6 server is not
>> sending "connection id" header back in its responses, so perhaps its a
>> double whammy.
>
> Hm, are you saying that if the server included the Connection ID in its
> GET-response, would that make it to the continue-GET (because of

i _think_ so

> OBEX_ObjectReParseHeaders() call)?

no, not because of that. OBEX_ObjectReParseHeaders() simply moves
parsed headers back to its original "un-parsed" state (as i understand
the code). so when the PUT callback invoked it will get access to the
same headers.

[combining emails]

> that patch does indeed make it work! fetching an 8k file with 4k MTU:
>
> (I have no time to think about possible misconsequences of this just now,
> perhaps I will subscribe to openobex-users mailing list and query them
> later)

thanks for trying it! could you please also try PUT (to and from
obexapp server) using wm6?

thanks,
max