Rana Thanks for the explanation. The hierarchy certainly makes sense, although I wonder about the methods to set the 2 observers. These don't effect the values at all, so perhaps do not need protecting within the internal IFtpStatistics. Maybe they could be moved into FtpStatistics?
- Dave. It was 18/01/2006 05:09, when Rana Bhattacharyya wrote: > Hi Dave, > > The FtpStatistics class hierarchy is like: > > FtpStatistics <-- IFtpStatistics <-- FtpStatisticsImpl > > FtpStatistics is supposed to be used in the Ftplet > environment where nobody should be allowed to set any > statistics value. Only the FTP server can change the > statistics value. So the FtpStatistics has no setter > methods. As the server has to set different statstics > values, internally IFtpStatistics will be used. "I" > prefix has been added to differentiate which will be > used internally by the server and which is exposed to > the Ftplet developers. > > You can always cast it to IFtpStatistics. But from > Ftplet point of view, it will be better to use Ftplet > instead. Then the custom code and core server code > separation will be clean. > > Thanks, > Rana Bhattacharyya
