Results 1 to 1 of 1

Thread: [2.0] IPC Remoting—Async Delegate Call Status

  1. #1

    Thread Starter
    I'm about to be a PowerPoster!
    Join Date
    Jan 2005
    Location
    Everywhere
    Posts
    13,647

    Arrow [2.0] IPC Remoting—Async Delegate Call Status

    Hi all,

    I'm using IPC remoting to send data between a service and a DLL. This works fine.
    I have a list of event subscribers that I loop through to broadcast a message.
    This is the code:

    Code:
    foreach (ClientServiceEventSink sink in _subscribers)
    {
      ClientRateUpdateHandler pf = sink.InvokeRateUpdated;
      pf.BeginInvoke(rateID, type, newValue, new AsyncCallback(onInvokeUpdate), null);
    }
    The sink object is derived from MarshalByRefObject and created by the client.
    Each subscriber has its own named pipe registered using its process ID.

    I'd like to modify the code so that I know when a message was unable to be sent due to a client disconnecting.
    Using Filemon, I can see that the message is sent and results in a "Pipe Closed" status. How can I programmatically trap this condition?


    Cheers,

    — P
    Last edited by penagate; Oct 31st, 2007 at 10:34 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width