Re: [orbitcpp-list] Re: perform_work, pending_work, can't work when blocking

[Brian M. <ba...@sn...>]

>>>>> "Sam" == Sam Couter <sa...@to...> writes:

    Sam> If you want a timeout event, then the best way is probably
    Sam> for the ORB to use the glib event loop instead of calling
    Sam> select() directly.

    Sam> There have been murmurs about the next version of ORBit using
    Sam> the glib event loop, which would make it possible to register
    Sam> your own timeout events. I don't know if that's still part of
    Sam> the plan. Multithreading support was also mentioned a few
    Sam> times, but again, I don't know if that's still part of the
    Sam> plan either. Would any ORBit developers (Elliot?) like to
    Sam> comment?

From <URL:http://icps.u-strasbg.fr/~genaud/ORBIT/x421.htm>

"Unfortunately, I don't really see how to do timeouts with the normal
CORBA event model, so I'm going to have to use the ORBit-specific hack
of having a glib event loop which supports both CORBA events and
timeouts. Another way, I am told, is something called an Evictor
pattern. I should understand this soon once I get my fancy CORBA book
in the mail.  The final way is just to leak memory like a sieve leaks
goldfish; this is the easiest thing to do."

1. What is the glib even loop? Is it or isn't it supported by ORBit?
2. What is the evictor pattern?

Of course, this document seems to be really old now (looks the same
last time I looked at it, 1 year+ ago), so not sure if it still
applies.
-- 
Brian May <ba...@sn...>