On Thu, Oct 30, 2008 at 3:31 PM, Jiří Kuhn <[EMAIL PROTECTED]> wrote: > if I want to use another ProtocolCodecFactory to use it within > ProtocolCodecFilter in NioListener I have to copy and paste > NioListener.start() method body and change just one line of code. That's not > too friendly. The hardcoded FtpServerProtocolCodecFactory (and FtpServer as > well) uses utf-8 charset for communication with clients. But not all clients > are UTF-8 aware. But non-utf-8 communication is another issue. To solve it, > it would be nice to be able easily extend NioListener to use another > protocol codec factory.
Since UTF-8 "extends" ASCII, is there another charset you like to use? Maybe we could provide the charset as a configuration in the core code? Can you suggest a client which does not work with UTF-8, I would like all clients to work with FtpServer so this would be important for us to fix! /niklas
