|
|
|
|
|
by eungyu
4944 days ago
|
|
Nice hack (although I would put this in the category of 'workaround'). The idea is cool, but I can already imagine all sorts of debugging nightmares with this approach. To begin with, how do we find out where the connection is broken (Is it the client socket or the proxy socket)? Bad connections have different reasons (in C terms: ECONNRESET, EWOULDBLOCK, ENETUNREACH, etc); are these specific reasons propagated verbatim? What about flow control between proxy and client? There is always a chasm between whipping up a cool hack and making something usable. This hack needs a long bridge in between. |
|