Patrick Ohly <patrick.o...@intel.com> writes: > deloptes <delop...@gmail.com> writes: >> On Mon, Aug 3, 2020 at 4:16 PM Patrick Ohly <patrick.o...@intel.com> wrote: >> >>> Emanoil Kotsev <delop...@yahoo.com> writes: >>> > Hi, >>> > It is the file UPGRADING.txt in openobex not the README >>> > Upgrading to version 1.7Upgrading to version 1.6 >>> >>> 1.7 is ancient (released 2016). I remember reading about "When using an >>> event loop that triggers on incoming data, you must call >>> OBEX_HandleInput() after each call to OBEX_Request() to actually send >>> the request" >>> (https://gitlab.com/openobex/mainline/-/blob/master/UPGRADING.txt). >>> If I remember correctly, my conclusion was that SyncEvolution does that, >>> but I am not sure anymore. >>> >>> >> I am also not sure where and how this has to be done. I think I have looked >> into SyncEvolution few years ago and it seemed to call OBEX_HandleInput(), >> but I am not quite sure at all. It could be also something completely >> different. > > Perhaps calling OBEX_HandleInput unconditionally after OBEX_Request is > really missing. I don't know exactly whether it now gets called only > when the fd is ready.
I wanted to try that out, but it turns out that all of my SyncML-capable phones are dead, i.e. I can no longer test the SyncML over OBEX code. I already bought a cheap used one via eBay, but that also was dead. I'll try with another one... -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- syncevolution@syncevolution.org To unsubscribe send an email to syncevolution-le...@syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
