architecture--it's implemented at the global level and for communities,
conferences still use the old hard-coded implementation. The new
StaticSecurityMonitor is configured via XML data, which will be important
when we implement the new Community Services architecture
files as they are likely to change VERY infrequently; this simplifies a lot
of bits of code that would otherwise have to call through VeniceEngine, etc.
Also folded the LocaleFactory class method into the new International object
used for managing the lists.
of "properties" storage and editing for conferences, communities, users, and
the global system. In addition, the "global properties" editing screen got
implemented, because it wasn't there yet.
to set their default language and time zone preferences; added footer text
and account signup accept/decline rules; added additional implementation
of dictyionary code for future; minor cleanup of rendering config; and
so forth
