Make sure data-book/cal is closed/freed in a separate thread
authorMilan Crha <mcrha@redhat.com>
Thu, 10 May 2012 10:54:16 +0000 (12:54 +0200)
committerMilan Crha <mcrha@redhat.com>
Thu, 10 May 2012 10:54:16 +0000 (12:54 +0200)
commit58f05268aa998f7720eb7a84c2d1abbdcb3f1c3d
tree5dfe1dafc305ae3c865b4e471bf28e4b69fc0e28
parent70e60c440f59c06610f27fb0280ba50754ea697b
Make sure data-book/cal is closed/freed in a separate thread

When EDataBook/EDataCal was unreffed in the main thread then
any later calls to the factory were blocked by the backend
till it freed its resources, possibly making client look like
frozen/unresponsive.
addressbook/libedata-book/e-data-book.c
calendar/libedata-cal/e-data-cal.c