My Seaport server regularly bombs with EPIPE exceptions especially in AWS. I assume these are broken dnode connection interruptions on the socket, right? it would be great if Seaport would recover from these and the layer handling the socket would bind on("error").
Error: write EPIPE
at errnoException (net.js:670:11)
at Object.afterWrite [as oncomplete] (net.js:503:19)
Am I right to assume it's at the dnode layer this should be handled?
should be fixed in #28