Zitat von Piotr Zgórecki <pzgore...@gmail.com>: > 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 > questions: > > 1. All existing users of the library will obviously suffer the same - > is this intentional ? > 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 ?
The bug for non-streaming is in obex_objec.c, line 417. The logic in inverted. It should be like in line 365. With streaming mode, there seems to also be a bug but only if you are trying to use it more advanced than it was possible with v1.5 (mixing body headers with other headers). Do you want to send patches or shall I do? HS ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
