I'm using the latest version of each component from version control as of yesterday.
I noticed where the notification code is disabled and re-enabled it. It isn't crashing for me, but does still have the issue of high CPU usage mentioned in a comment in the notification callback. I made a change in openchange to fix that. Otherwise, it seems stable, it just doesn't actually trigger any notifications. From Brad's response, it sounds like I can fix that problem on the evolution-mapi side, so hopefully I can get the notifications working soon. Thanks, Aaron On Wed, Aug 31, 2011 at 12:46 AM, Milan Crha <mc...@redhat.com> wrote: > On Tue, 2011-08-30 at 21:15 -0400, Aaron Small wrote: >> Looking >> through the code, I see that it doesn't call RegisterAsyncNotification >> like test_asyncnotif, but instead calls >> RegisterNotification/Subscribe/MonitorNotification. Evolution-mapi >> calls the same sequence of >> RegisterNotification/Subscribe/MonitorNotification, and has the same >> problem of not being notified when new mail arrives. > > Hi, > just out of curiosity, what version of openchange and evolution-mapi are > you using, please? The latest evo-mapi has notifications disabled, > because it was causing crashes. Now, that evo-mapi 3.1.90 depends on > openchange 0.11, with a bit of rewrite, the code would be reenabled > again. But I've no promises when it will happen. > Bye, > Milan > > _______________________________________________ > devel mailing list > devel@lists.openchange.org > http://mailman.openchange.org/listinfo/devel > _______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
