[omniORB] processing COMM_FAILURE_UnMarshalArguments

[vadim A]

2009/3/13 Duncan Grisby <duncan at grisby.org>

> On Friday 13 March, vadim A wrote:
>
> > Can i processing COMM_FAILURE_UnMarshalArguments message for deleting
> servant?
>
> Do you mean can you get the server-side to detect when a client
> disconnects, and delete your servant in response?  If that's what you
> mean then, no, you can't do that. Clients are permitted to close their
> connections at any time, and open new ones when required, so using
> connection closure to deactivate a servant would be the wrong thing to
> do.
>
> Cheers,
>
> Duncan.
>
> --
>  -- Duncan Grisby         --
>  -- duncan at grisby.org     --
>   -- http://www.grisby.org --
>
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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20090313/6f2b5544/attachment.htm