<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I assume you mean calling poa->deactivate_object() ?</blockquote>
<div><br>Yes.<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The CORBA spec doesn't say a huge amount about the main thread model.<br>
All it says is that "upcalls" are handled by the "main" thread, but it<br>
doesn't specify what constitutes an upcall. </blockquote><div><br>I noticed it -- that is why I used "almost violation".<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
you can force use of the main<br>
thread by registering a ServantActivator that is itself activated in a<br>
POA with the main thread policy. That way, servants will be released<br>
using a call the etherealize() on the ServantActivator, which will<br>
happen on the main thread.<br>
<font color="#888888"></font></blockquote><div><br>Thanks, Duncan!<br></div></div><br>