Hello Patrick, Somehow i was able to modify the devinf information being sent from client to remote Server. Had to hack the libsynthesis code for this. Though the engine still dumps the original devinf in outgoing.xml, server gets the modified devinf.
I modified the syncagent.cpp of libsynthesis code in function TSyncAgent::NextMessage just before it enters FinishMessage and replace the already formed DevInf information. Sync happened with the modified devinf, but am not sure what are the repurcussions of modifiying the devinf in memory on client side. How will the client behave to syncs sent from server? Can you think/suggest some issues or cases which i can test this change? Regards On Fri, Nov 22, 2013 at 2:08 PM, Patrick Ohly <[email protected]> wrote: > On Fr, 2013-11-22 at 13:22 +0530, Sachin Gupta wrote: >> Hi, >> >> Can you point me to the code piece where Syncevo prepares and provides >> the input to synthesis. >> >> Please elaborate more on Source which Syncevo enables. What are these >> and how are these enabled? > > Have you read the libsynthesis/doc/SySync_config_reference.pdf and > SDK_manual.pdf? This explains all options offered by the Synthesis > engine. Once you know what to look for, just grep the SyncEvolution > source code, for example: > > git grep -i "<datastore" > ... > src/syncevo/SyncContext.cpp: datastores << " <datastore name='" > << name << "' type='plugin'>\n" << > ... > > There's also this introduction: > https://syncevolution.org/development/pim-data-synchronization-why-it-so-hard > > -- > 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] https://lists.syncevolution.org/mailman/listinfo/syncevolution
