On Di, 2011-07-19 at 10:29 +0200, Patrick Ohly wrote: > On Fr, 2011-07-15 at 13:12 +0100, Andy Gould wrote: > > On 15/07/11 12:58, Patrick Ohly wrote: > > > On Fr, 2011-07-15 at 12:44 +0100, Andy Gould wrote: > > >> On 15/07/11 11:42, Patrick Ohly wrote: > > >>> On Fr, 2011-07-15 at 11:21 +0100, Andy Gould wrote: > > >> Hi Patrick, > > >> I may have misunderstood the point of the 2 activsyncd accounts ( Foo, > > >> and Foo_B in gconf) - can you clarify for me.... should they point to > > >> different Exchange accounts ( [email protected] and > > >> [email protected]) - or the same one? > > > The same one, but with different device IDs. > > > > > > 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. One more > > modification, and hopefully that will sort it.... getting there slowly. > > How has this been resolved? Is it necessary to manually request real > unique device IDs in gconf for the second Foo_B account?
Found this commit: commit e0a9cf7ec000c782ccecee26a5f4c5caadff9365 Author: Andy Gould <[email protected]> Date: Fri Jul 15 15:50:18 2011 +0100 adding support for fake device ids in g-conf. If a device id is added to the gconf account, use that instead of the device wide one. updated connection hash table to use device id A side note: please hard-wrap git commit messages. This is one long line, which does not display well when using "git log". Do we have documentation for activesyncd, or is it all just "read the source"? In this case the code shows that a new "device_id" gconf key is read, but it doesn't explain what valid strings are. Can I just make up my own? -- 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
