Hi, I've just got a basic FTP server module working. However, it's working with some built-in defaults that the administrator needs to configure, most importantly the FTP port itself (by default it will be 8021, do you think it's a good default?)
So I need to roll out a configuration object and manage storage for it, and I would really like to avoid rolling yet another property file... would feel quite a bit better to be able to use a GeoServer pluggable extension point instead. Now FTP is a service, so ServiceInfo would seem like a match... there are however a couple of issues: - there is a number of extra things there that are OGC specific (I guess I could just ignore them) - a FTP capabilities link will pop up in them main page if I go that way. Soo... what shall we do? I guess an easy way would be to add a flag in the ServiceInfo object, isOGCService() to mark the ogc services (on by default) or else to roll out a subinterface, OGCServiceInfo, or a marker interface, OGCService.... Opinions? In general, how would you address pluggable configuration storage? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
