On Wed, 2009-09-02 at 02:04 +0100, Zhu, Yongsheng wrote: > > We'll need to add something to the API, I guess. Status "running" could > > be divided into "processing" and "waiting"? > Good, I like this idea to tell users more information about status. But > should we > give more detailed information,
It'll be hard to obtain such detailed information. Also, in most of the local cases we have reliable progress information and then don't need the spinner (= "waiting for someone else"). > such as 'checking data in the evolution(backend)', That's covered by the "preparing" progress. > 'send data to server', 'waiting for server response', 'receive data from > server', I'm not sure whether we can get such detailed information from libcurl or libsoup. Given the libsoup design I doubt it. > 'apply data to backend' and others? That's when we report progress about items received. How about not deciding this issue just yet? We can define "processing" and "waiting" as taking an option parameter after a colon, like this: "waiting:network". Clients which don't care simply do a prefix check for "waiting". If we find a use for more detailed information, we can add it without breaking the API. -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Open Source Technology Center Hermuelheimer Strasse 8a Phone: +49-2232-2090-30 50321 Bruehl Fax: +49-2232-2090-29 Germany _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
