Am Montag, den 28.06.2010, 14:42 +0200 schrieb Patrick Ohly: > On Fr, 2010-06-18 at 09:14 +0100, Patrick Ohly wrote: > > I'll start filing issues with API proposals. > > Below a summary of the proposed enhancements. Does that sound right?
Looks all right, thanks for picking up my proposals! > Do > we need additional flags for starting a session, beyond the "not for > sync"? Hm, I couldn’t find the flags defined for StartSessionWithFlags. Originally, I thought this could also be used for starting sync sessions. As I discussed earlier with Jussi (and if I understood everything correctly), there is an inherent race condition in the way sync sessions are created, because one has to request the session, then connect to the SessionChanged signal and launch the sync once the SessionChanged signal comes in (which might be before the signal was connected). So I thought one could work around this by calling a session with a "meant for sync" flag, but then a client would also have to know that a particular session was requested by itself, not by another client. So this was probably a bad idea, and it is enough to know that a session was not meant for syncing, as proposed. Sorry for thinking aloud, I just thought I might have overlooked something that someone else can see clearer. > How urgent is this, in other words, who wants to use these extensions at > which point in time? For me (and Genesis) all this is not really urgent. It currently works, so this would be welcome polish, but not really new features. (Maybe except for the Session.GetConfigName() method, since this might be a relevant information that is currently lacking from sync reports.) Once syncevo-dbus-server implements these (and binary pre-releases are available, I’m too lazy for building it myself ;)), I’ll implement the corresponding functionality in Genesis. So no hurry from my side. Cheers Frederik _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
