[Discussion] Handle client sudden disconnections about ftpserverlib HOT 2 CLOSED

I think it would be good idea to attach context.Context to ClientContext so implementations can react to closed connection. It would be good to do so even before you figure out how to properly detect it

from ftpserverlib.

I'm closing this because:

• We are the root of a possible context, the library is not doing anything cancellable, it's only reacting to short commands and piping streams. So I think it makes sense but on the client driver implementation and as such, I'll leave it to the client drivers (in this case the afero ones) to use it.
• I don't see any place where it could make sense, to be more specific:
  • If a control connection closes, it doesn't mean the transfer connection should be canceled
  • If a transfer connection closes, then that's the end of the file

from ftpserverlib.