Description Ed Swartz 2010-09-16 13:16:26 EDT

EDC can create TCF channels on behalf of clients but is not listening to errors or close events on those channels.  

Thus, when debugging under EDC and a debug agent dies or a device is disconnected, the EDC session will usually sit waiting for a long time.  Terminating the session through the UI will further hang because EDC tries to send commands on the dead channel and wait for responses.

Also, just in general, it's a bit of a hack in other parts of EDC to interact with peers and channels that EDC has created internally (i.e. via TCFServiceManager#getPeerService).  ITCFServiceManager only exposes a way to get an existing channel on a peer, but no way to directly discover what channels it has opened internally on a peer via #getChannelForPeer().  

I propose solving both of these problems in a general way by allowing clients to register a listeners on ITCFServiceManager, which informs when an IPeer/IChannel combination is opened or closed.  

Then, the AbstractFinalLaunchSequence#initFindPeerStep() can add such a listener and terminate the debug session when its peer/channel tuple dies.

QUESTION: what is the proposed way to alert the user when the debug session is killed?  I.e. are we allowed to put up UI?