Bug #2869

NFD Restart Breaks Face Socket

Added by Andrew Brown over 6 years ago. Updated over 5 years ago.

Start date:
Due date:
% Done:


Estimated time:


If a Face is connected to a remote NFD using TcpTransport, an NFD restart will break the TCP socket. If the default constructor is used, the user does not have a reference to the transport to call transport.connect() and re-connect the TCP socket; repeated calls to face.processEvents() will fail without attempting to reconnect. Don't know if this is a bug or a feature request and haven't tested with other transport types. Possible solutions:

1) make transport.processEvents() attempt to reconnect the broken socket
2) allow users access to the transport from the face so that they can re-connect it
3) force users to pass in a transport instance and keep a reference to it alongside the face reference; write code to trap a face.processEvents() error and trigger a transport.connect (I don't like this option as much)


Updated by Jeff Thompson over 6 years ago

Hi Andrew. Your option number 2 looks like feature request #2075 for the library to inform the application when the connection drops. Maybe we can copy your suggestions and continue the discussion there?


Updated by Jeff Thompson over 5 years ago

Hi Andrew. Can we close this in favor of the discussion on issue #2075 "inform the application when the connection is lost"?


Updated by Andrew Brown over 5 years ago

Yes, let's close it.


Updated by Jeff Thompson over 5 years ago

  • Status changed from New to Closed

The conversation has moved to issue #2075. Closed.

Also available in: Atom PDF