Ok, thank you henrik.<div>So I understand well that the announcement delivery handler will recast in new thread. The point I do not get (and maybe its obvious, sorry in advance), is why does it raise an error ?�</div><div>
When I look at the debugger, it seems that at one moment in the on:fork: method we got a &#39;context&#39; that is nil whereas it should not.�</div><div>It is quite to understand what is problem (As I do not have a lot of knowledge around that)<br>
<br><div class="gmail_quote">2011/6/28 Henrik Johansen <span dir="ltr">&lt;<a href="mailto:henrik.s.johansen@veloxit.no">henrik.s.johansen@veloxit.no</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><br><div><div class="im"><div>On Jun 28, 2011, at 10:23 56AM, Cyrille Delaunay wrote:</div><br><blockquote type="cite">I got another issue related to that i think.<div>In moose , at one moment in a announcement handling code, we are �doing:�Notification signal: &#39;Save successful!&#39;.</div>
<div>That has for consequence that the on:fork: cuts the stack and I end up with a &#39;MessageNotUnderstood: receiver of &quot;sender&quot; is nil&#39;.</div>
<div>So I don&#39;t know if the problem is that we are signaling a notification? </div></blockquote><br></div><div>Yes, if nothing inside the announcement handling code handles it, it will get handled by the announcement delivery handler which recasts it in new thread, for the reason Igor mentioned below.</div>
<div>It&#39;s not safe to simply pass it on for handling by the code that made the announcement, if you want to ensure delivery.</div><div class="im"><div><br></div><br><blockquote type="cite"><div>if yes what should we use to notify something ?�</div>
</blockquote><div><br></div></div>... an Announcement?</div><div class="im"><div><br><blockquote type="cite"><div><div><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
It was because on:fork: cuts the stack.<br>
If you signaling exception in your code, you should handle it before<br>
leaving your #actionSelector method.<br>
Otherwise you may put the rest recipients of announcement in danger<br>
and that&#39;s why there #on:fork: to prevent that.<br>
<font color="#888888"><br>
<br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
<br>
</font></blockquote></div></div></div></div></div></blockquote></div><br><div><br></div><div><br></div></div><div>Cheers,</div><div>Henry</div></div></blockquote></div><br></div>