iMo Communities

The performance of the user-interface is not as good as are our end-users want it to be. Specially the first-time a screen is started the performance is bad. It's menu's, images and translations are fetched for the first time. The performance loss is mainly in the AppServer roundtrips. To avoid extra roundtrips we decided to preload the translations. We discovered the time needed to fetch the translations of the mainmenu and maintoolbar is more than the time needed to fetch all translations (4464 records) at once.
Because we only need to support a single language this workaround could stay rather simple.
Imo release 2009-D will implement translation caching, for the time being you could use this workaround ( >= iMo20090213).

Workaround: The TranslationManager fetches all translations the first time it's being referenced. To keep this workaround simple we assumed the language of the user is the default application language. To fetch the translations we should have implemented a new method in the beTranslationManager. Because all supporting methods for this functionality are private methods of the daTranslationManager we decided to implement this workaround in the daTranslationManager. This implementation should not be used as an example, it's is made to get results quickly.