The creation of the FtpServerListenerService object in the FtpServer constructor is great for people who don't mind this library managing Tcp connections but not for people like me who already have a framework in place to manage and monitor these. Consider allowing a 'IPausableFtpService' interface or similar to be passed in via a constructor overload. That way I can manage the TcpClient object differently.