Hello Patrick, On Feb 18, 2010, at 17:53 , Patrick Ohly wrote:
> On Mi, 2010-02-17 at 17:29 +0000, Lukas Zeller wrote: >> The big problem is that the device (Nokia phone) usually asks for the >> server devInf BEFORE it sends it's own devInf, but the server can't >> detect what device it is talking to before receiving devInf. > > Asking for DevInf before sending its own would probably confuse even > more devices, right? Probably. Without checking details, IMHO the standard would allow to delay the <Results> for a <Get>, but that would imply that the init phase would be extended to have two message exchanges. Given all the troubles we've seen with <final/> statemachine handling, it's likely to cause problems. > Speaking of confused, I'm a bit confused about CTCap inside DevInf right > now. In the SyncEvolution client <-> SyncEvolution server scenario, the > client sends DevInf including CTCap to the server in its first message. > The server sends DevInf in its reply, but without any CTCap. I don't > have <showctcapproperties> in my config. > > I would expect to see the server's CTCap in the session. Any idea why it > is not sent? The only reason I can think of right now would be a too small message size, which the devInf exceeds. If that happens, CTCap is left out to make the devInf sendable, because <results> can't be split across messages. Lukas Zeller ([email protected]) - Synthesis AG, SyncML Solutions & Sustainable Software Concepts [email protected], http://www.synthesis.ch _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
