Home/ Questions/Q 889873
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T13:38:07+00:00

I’ve implemented a task using the async Sockets pattern in Silverlight 3. I started

  • 0

I’ve implemented a task using the async Sockets pattern in Silverlight 3. I started with Michael Schwarz’s implementation and built on top of that. So basically, my Silverlight app establishes a persistent socket connection to a device and then data flows both ways as necessary between the device and the Silverlight app.

One thing I am struggling with is how to detect disconnection. I could think of 2 approaches:

  1. Keep-Alive. I know this can be done at the Sockets level, but I am not sure how to do this in an async model. How would the Socket class let me know there has been a disconnection.

  2. Manual keep alive. Basically, I am having the Silverlight app send a dummy packet every 20 seconds or so. If it fails, I’d assume disconnection. However, incredibly, SocketAsyncEventArgs.SocketError always reports success, even if I simply unplug the device that the Silverlight app is connected to. I am not sure whether this is a bug or what or perhaps I need to upgrade to SL4.

Any ideas, direction or implementation would be appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I ended up going with a heartbeat packet that requires an answer from the target. Basically, I send a predefined dummy packet and the target device must respond with the same, otherwise the connection is considered invalid.

    • 0