On Fri, May 14, 2010 at 02:17:01PM +0000, Tim Donohue (JIRA) wrote: > (Sidenote: Eventually, someday, I feel we should move the majority of all > configurations to the Admin UI -- so that there's no need to stop/start > Tomcat/DSpace every time you need to modify dspace.cfg. However, in order to > achieve this, we need to *trust* that the System Administrator knows what > he/she is doing -- they should be allowed to make any change in the system.)
If runtime reconfiguration is a goal, we need to agree on it (and I'm
not disagreeing here) and then go through the code to make sure that
we *always* call the ConfigurationManager for settings instead of
e.g. caching config. data via static initializers.
Item for next week's agenda?
We'll also need to stare hard at each of the configuration variables
and work out which ones make sense to adjust at runtime.
Absolutely, the sysadmin. is allowed to break anything, so long as he
is prepared to answer for it. :-) I expect that (both aspects) when I
wear my sysadmin. hat.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgpAP6N06da1b.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
