Configuration scope

_From [kevinb9n](https://code.google.com/u/113026104107031516488/) on February 28, 2007 15:51:25_

This would be a scope that anything that reads from modifiable
configuration sources (database, xml/props file, etc.) could live at.  Then
we'd provide a means by which an administrator can send a reload message to
a running server (JMX, perhaps?).  When the message is received, the
current configuration scope would become a "lame duck" while the objects
for the next configuration scope are all reconstructred; when
reconstruction is finished we'd invalidate the old configuration scope and
start serving requests out of the new.

I wonder if we'd have to be careful that each single request scope uses
only one configuration instance and never a mixture of old and new.

This is the rough idea though; comments?

_Original issue: http://code.google.com/p/google-guice/issues/detail?id=48_