Painful issue here - we all know the regular drill of maintaining
messages in many places, I18N files and so on.
Also there's a patch to make all available timezone an java enum and by
that share it for free with the UI. its a way better than a backend Query.
But this is all hard-coded, not flexible, hard to maintain, we all know.
servlet or our host page html using GWT Dictionary?
that way the configuration is shared with the engine, it relies on the
disk, customers and GSS can change it on-site and so on.
| index.html | -> | file servlet | -> |read /etc/ovirt-engine/conf/...|
| GWT loads Dictionary |
candidates for dynamic resources
* I18N resources AppErrors...
* config ( just the UI subset )
* osinfo ?
 host page html -
 Dynamic string internationalisation -