https://bugs.freedesktop.org/show_bug.cgi?id=60851
--- Comment #2 from Patrick Ohly <[email protected]> --- I also found that a ReadContacts() call with a large number of ids can lock up the server for a while, because *that* call is implemented synchronously. I looked briefly into what it would take to make it asynchronous, but stopped after thinking about some of the consequence. By design, the call has to return all results at once. That implies assembling the response in memory and returning it when done. When interleaving other event processing with that data gathering, the result might become inconsistent (contact prepared, stored, then modified before sending result). Preventing that is much harder than letting the application break up large ReadContacts() calls into multiple smaller ones. This is what I am now doing in testpim.py. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
