Hello Patrick, On Jan 29, 2010, at 19:03 , Patrick Ohly wrote:
> I think I ran into the following situation: > * a sync session was suspended on the server because the client > stopped sending messages > * in the next sync, the client wanted to start from scratch and > used "refresh-from-client" mode, not knowing (or caring) that > the server expected it to resume > * the server denied the accces with status code 403, which we show > as "log in succeeded, but server refuses access - contact server > operator" > > Client and server were both SyncEvolution. > > Does this sound plausible? I can try to reproduce it, if necessary. No, it's fully up to the client to try a resume or just do another sync, with any mode it chooses. The server is not in a position to expect anything from the client - it just has to execute for what it gets alerted by the client. The server cannot not even know if a client supports Suspend&Resume (until the client tries it for the first time, of course). So that must be a bug - or something not directly related to the suspend. Do you have logs of the situation? If not - yes, please try to reproduce it, as I have no idea where to start doing that in my setup here (implicit suspends happen all the time here, and I've never seen that 403 so far). > What is the expected outcome? IMHO, the server should do a > refresh-from-client. Yes - the server must simply do what the client says. The only option it has is to reject a resume, or request a slow(or refresh) on anchor mismatch. Best Regards, Lukas Zeller ([email protected]) - Synthesis AG, SyncML Solutions & Sustainable Software Concepts [email protected], http://www.synthesis.ch _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
