>Hmm, this would have been another way for a Connection to set "no need > to authenticate". Should I remove the parameter again? If there is an existing way for this, I'm inclined to remove it.
Cheers, Yongsheng -----Original Message----- From: Ohly, Patrick Sent: Friday, November 06, 2009 10:37 PM To: Zhu, Yongsheng Cc: SyncEvolution Subject: RE: code review: automatic D-Bus testing + Session.Sync() On Fri, 2009-11-06 at 13:59 +0000, Zhu, Yongsheng wrote: > Is 'mustauthenciate' used only internally? At the moment, yes. It is used to implement the sync via a Connection. > If no, we might change the API. If yes, we currently hardcode it. > Seem strange. Session.Sync() is meant to be used for initiating a sync from the GUI. When we act as client, there's is no need for "mustauthenticate", it wouldn't have any effect (our clients always send credentials, even if they are not required to). When we act as server, the caller could temporarily reset username and password to get the same effect. Hmm, this would have been another way for a Connection to set "no need to authenticate". Should I remove the parameter again? -- 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
