On Fri, 2009-07-31 at 12:43 +0100, Lukas Zeller wrote:
> Furthermore, If I remember correctly, a sync session in OBEX runs
> within a single OBEX session anyway (unlike HTTP), so if that
> transport level session breaks, a new SyncML session must be started
> anyway.
You remember correctly.
Hello,
the "experiments where devices were disconnected while a session ran
and it continued seamlessly after reconnecting" were with HTTP (e.g.
devices connected to the internet via WLAN, and reconnecting over GPRS
when walking out of WLAN coverage).
I must admit that I don't have a lot
Hello!
As discussed here in an earlier thread, when clients don't get a reply
to their HTTP POST, they can resend that message and that way work
around half-open TCP connections. It may also be a good idea in case of
other, detected network problems.
Over on the SyncEvolution list we we are now d
