Re: [Evolution-hackers] Re: Strange console messages when accessing e-d-s through the libecal C API
- From: Not Zed <notzed ximian com>
- To: vseguip gmail com
- Cc: evolution-hackers lists ximian com, michael meeks novell com
- Subject: Re: [Evolution-hackers] Re: Strange console messages when accessing e-d-s through the libecal C API
- Date: Wed, 24 Aug 2005 10:19:47 +0800
On Tue, 2005-08-23 at 18:12 +0200, vseguip gmail com wrote:
> Hi Michael,
>
> On 8/23/05, michael meeks <michael meeks novell com> wrote:
> >
> >
> > On Tue, 2005-08-23 at 17:45 +0200, vseguip gmail com wrote:
> > > > you need to grab ORBit2 and work out why no-one else is seeing the
> > > > message - cf. ORBit2/src/orb/orb-core/* somewhere or perhaps
> > > > ORBit2/linc/src/*
> >
> > Nah - I mean why other C apps are not seeing the message - why doesn't
> > eg. 'evolution' itself see it.
> >
My original reply said this was probably because the code isn't running
in a main loop. It therefore has no proper way to handle idle-processed
return corba calls if they come in after an invocation returns. I think
the eds objects use idle-return processing for its calls, not threads.
I got the same problem when i was testing the mail-remote api from a
simple client, until i ran things in a mainloop. This started when i
added listener objects and they started being called.
I don't think it's a bug in the code so much as a mis-use of it.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]