Am Dienstag, 21. Juni 2011, 18:56:30 schrieb Piotr Zgórecki:
> I played a bit with the obex_test program to understand OpenOBEX and
> PUTs wouldn't work.
> That's because the test app doesn't append an empty BODY header at the
> end, which is now required with API changes introduced by the
> aforementioned commit to properly generate an END_BODY. So - a few
> 1. All existing users of the library will obviously suffer the same -
> is this intentional ?
No, it is not.
> 2. I'm trying to understand the merit of the change and I think I'm
> missing something - the commit message says it's for applications to
> be able to insert headers in between BODY headers. However, given that
> both obex_object_addheader() and obex_object_send() seem to preserve
> the order of headers fed by the application that ability had always
> been there. Are there any scenarios I'm missing ?
Yes. The receiver might interpret the END-OF-BODY header as the end of the
object, as specified by the OBEX spec.
The intention was to not send an END-OF-BODY header if there are other headers
after the BODY header _at_ _the_ _time_ that the stream is empty.
I take a look at it.