On Wed, Oct 15, 2003 at 02:32:56AM -0500, Pascal wrote: > There are currently two different methods of changing the config on the > fly. You can either place a method inside > NodeConfigUpdater.ConfigOptions or use the addUpdateListener method. > The main difference between the two is when the ability to update an > options gets registered. NodeConfigUpdater.ConfigOptions is read at > compile time while addUpdateListener is updated at runtime. The options > in NodeConfigUpdater.ConfigOptions can be spit out to whatever program > happens to launch fred so it can determine if it needs to restart the > node for a particular config change. This behavior was requested, and I > implemented it in fred, but I am not sure if the windows launcher > currently implements it. Bottom line, if you want the launchers to know > the option can be updated without a restart you'll have to use > NodeConfigUpdater.ConfigOptions. > > One of the problem that has been reported with > NodeConfigUpdater.ConfigOptions is that it does not support options with > a period in them as java method names do not. If you want to code up > support for an option with a period your will have to do some kind of > substitution for it. Perhaps use hyphens in the method names, and > before the reflect search the modified options for periods and replace > them with hyphens.
Incorrect. This is quite possible. Using the config updater callbacks. See freenet/node/http/infolets/DefaultInfolet.java. > > -Pascal -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
