I tried that but it did not resolve the problem, which I think means
that I'm not using the correct approach as I expect reset would succeed
:-). The "connect events" are processed on the second call to
handle_events, after the first call to handle_events returns.
I've tried the reactor->notify(,,,) approach as well but it did not work
straight off so I will do some more testing of that just to prove to
myself that I understand how it is intended to work.
I think the right approach for this problem is to use a condition
variable on which the main thread will wait until it can do the next
From: XXXX@XXXXX.COM [mailto: XXXX@XXXXX.COM ]
Sent: 24 April 2007 18:32
To: David Gibbs
Subject: Re: [ace-users] reactor handle events and event handlers
Thanks for the PRF.
Yes, indeed - they get removed only when you explicitly remove them or
when the Reactor's destructor is called.
Did you try calling
ACE_Reactor::instance ()->reset_reactor_event_loop ();
so that the event loop can be restarted?
The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone +44 (0)20 7896 0011 and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. IG Markets Limited and IG Index Plc are authorised and regulated by the Financial Services Authority and, in Australia, by the Australian Securities and Investments Commission.