On 11/07/11 17:20, Patrick Ohly wrote:
On Fr, 2011-07-08 at 18:09 +0200, Patrick Ohly wrote:
Is suspect that part of the problem is that Client::eas_event::Source
needs to "simulate" access by two different clients. Both use the
ActiveSync account defined by
~/.config/syncevolution/client-test/peers/target-config/config.ini
so essentially this looks to the Exchange server like one client.
I fixed this with the following commit:
commit 6300b3ea9184e114b521ef2e5eafda476c836e5c
Author: Patrick Ohly<[email protected]>
Date: Mon Jul 11 14:40:06 2011 +0200
Hi Patrick,
Having fixed the duplicating issue, I'm still seeing invalid sync
keys, but I think this is a problem in how the tests are trying to
work... from the point of view of the Exchange server, this is still
looking like one client, because it uses a device id, and the username (
the activesync account id is only a local identifier)... I'm going to
try account level faked device ids for the purposes of testing, and see
if that works..
Andy
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
