<br><br><div class="gmail_quote">2009/3/13 Duncan Grisby <span dir="ltr"><<a href="mailto:duncan@grisby.org">duncan@grisby.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Friday 13 March, vadim A wrote:<br>
<br>
> Can i processing COMM_FAILURE_UnMarshalArguments message for deleting servant?<br>
<br>
</div>Do you mean can you get the server-side to detect when a client<br>
disconnects, and delete your servant in response? If that's what you<br>
mean then, no, you can't do that. Clients are permitted to close their<br>
connections at any time, and open new ones when required, so using<br>
connection closure to deactivate a servant would be the wrong thing to<br>
do.<br>
<br>
Cheers,<br>
<br>
Duncan.<br>
<font color="#888888"><br>
--<br>
-- Duncan Grisby --<br>
-- <a href="mailto:duncan@grisby.org">duncan@grisby.org</a> --<br>
-- <a href="http://www.grisby.org" target="_blank">http://www.grisby.org</a> --<br>
</font></blockquote></div>For normal switching-off of the client I use a method disconnect. A problem of processing of abnormal switching-off a server for example in a consequence segfault. The variant with use callback a method is undesirable. How it can be organised?<br>