On Fr, 2011-07-15 at 13:12 +0100, Andy Gould wrote: > On 15/07/11 12:58, Patrick Ohly wrote: > > So if you configure target-config@client-test with username=Foo, then > > you need accounts called "Foo" and "Foo_B" in gconf. Both must have the > > same username/password/URL. But because they are different local > > accounts, my expectation is that activesyncd treats them completely > > separate and thus assigns different device IDs. To the Exchange servers > > this should look like two devices who happen to contact it with the same > > IP address. > > > yeah, thats what I thought unfortunately, your assumption about the way > that the accounts are handled was not correct. At the moment, the > device id is exactly that - fixed for the device, so I needed to > allocate account level ids instead, I have done that - but they are not > being used, because the daemon is too clever for its own good - and > recognises that the 2nd account is actually pointing at the same > Exchange account, and grabs the existing connection for it.
That's indeed way too clever. Remember that the account and thus the activesyncd may be shared by multiple, independent pieces of software. They need to cooperate on the creation of the gconf configs, but they shouldn't be forced to coordinate their access to those configs once that is done. Therefore different configs really must be completely separate. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
