[cosmo-dev] db-stored server configuration

[Jared Rhine]

> Jared- any perspective as a server admin?

Having the properties in a table is nice, but *strictly* a nice to  
have.  My Hub users' lives will not be the tiniest bit better if  
configuration moves to a database table.

Once a year, maybe, I could avoid 20 seconds of downtime caused by  
restarting the server.  Putting things in tables doesn't actually make  
it easier to manage for an admin.  In the majority of cases, editing  
files is more efficient than navigating a web UI or starting a mysql  
shell.  So the argument for such a feature shouldn't be based on  
"easier for admins" at least; the stronger argument seems to be the  
"avoid a restart" argument (note, only applies for some features; most  
of my config changes have been server.xml, log4j.xml, etc which would  
still need restarts.)

I personally would not allocate any developer time, pre 1.0, towards  
support for changing a configuration property without a server restart.

(In an ideal world, I would of course +1 a properties-in-a-table  
feature.  The argument above is strictly a "don't we have better  
features to allocate time towards?" one.)

-- Jared