On Fri, Nov 27, 2009 at 4:51 PM, Dave Roberts <[email protected]> wrote: > 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?
Yes, I think that should be the plan. The main reason they are currently pushed into the private packages is that there's some work needed to get these classes working from the concurrency standpoint (immutable classes is be prefer). > 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. Agreed. I do not have any opinions on the preferred API for this. Further ideas and patches welcome of course :-) /niklas
