[evolution-mapi] Bug #607527 - 100% CPU usage after push notification changes.

[Johnny Jacob <jjohnny src gnome org>]

commit d7ec3455ba6be9ba0040ce4368926c82c6d1d32e
Author: Johnny Jacob <johnnyjacob gmail com>
Date:   Thu Jan 21 17:14:21 2010 +0530

        Bug #607527 - 100% CPU usage after push notification changes.
    
        Bug in libmapi 0.9 MonitorNotification causes select() to return immediately instead of waiting. So introduced a artificial delay in evolution-mapi to avoid high CPU usage.

 src/camel/camel-mapi-notifications.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
---
diff --git a/src/camel/camel-mapi-notifications.c b/src/camel/camel-mapi-notifications.c
index a06ff2e..58e1065 100644
--- a/src/camel/camel-mapi-notifications.c
+++ b/src/camel/camel-mapi-notifications.c
@@ -228,6 +228,11 @@ mapi_notifications_continue_check (gpointer data)
 	if (camel_operation_cancel_check(NULL) || (camel_application_is_exiting == TRUE))
 		return 1;
 
+	/* HACK ALERT : This is a BAD idea. But ;-), A bug in MonitorNotification */
+	/* makes select() return immediately. We are introducing a artificial delay here */
+	/* to avoid high CPU usage. Remove this when libmapi 0.9.1 is out */
+	g_usleep (G_USEC_PER_SEC * 2);
+
 	return 0;
 }