It's all the same to me. Most of the time the key stuff shouldn't need the config file, it is only when people add new key classes that weren't known when Core.java was compiled (I guess if there is absolutely no support for dynamic loading in compiled java that would have to go too).
Almost every program I know has a section in the config file that says "Users should normally not have to worry about editing this". Users who can't understand that line (and you know they are out there) have no business editing the config manually anyways. On Sat, 05 Aug 2000, Brandon wrote: > > Actually all Messages, Addresses, Connections and Listeners are loaded > > dynamically (Class.forName()). That is the way that all these things were > > originally made pluggable. > > > > Being able to compile is reason enough to change this anyways IMO. Something > > like what I did with the keys should be fine. > > I think that the current key configuration code should go in a separate > file. .freenetrc is meant to be editted by users. Things that users should > not edit should be somewhere else. In the jar file, loaded as a resource > would be a good place for it. > > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
