Back in the day, I would get a copy of the FtpServerContext and from that get the ServerFtpStatistics which I would use to call the setFileObserver() method. However, this involves a lot of casting and use of "internal" classes and interfaces.
Given that setting Observers would seem to be something that developers embedding the FTP Server are likely to want to do, would it not make sense to expose these methods somehow? The simplest idea would seem to be to push the methods up to the FtpStatistics interface. However, these are only exposed through the Ftplet which are runtime objects. I don't think we want people to create an Ftplet just to set an Observer. To me, setting the Observers is part of the configuration and perhaps is better placed within that mechanism. Comments?
