<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 19, 2011, at 2:03 PM, Fabian Rothfuchs wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">The second important part was the wakeUp() call, which apparently triggers<br>the reactor<br>To end all blocking tasks.<br></span></span></blockquote></div><br><div>For the most part, you have got the right idea now, but this is a BIG flashing red light for me. wakeUp() shouldn't actually be a public method at all; its _only_ use is as part of the implementation of 'callFromThread'. You should never, ever call it, and if you do call it, it should appear to do nothing at all.</div><div><br></div><div>Are you making use of the reactor from multiple threads? This is not allowed, and will break horribly, although it can sometimes (briefly) be made to appear to work by calling wakeUp().</div><div><br></div><div>-glyph</div></body></html>