I posted this same question a few months back but didn't really get any answers that helped me decide on what to do. So here goes again:
The thing I've been looking at Internationalization issues concerned with Struts. The thought of being able to change the whole language of a site simply by changing the locale of the user really appeals to me. All examples i've seen so far use parallel versions of the ApplicationResources.properties file to accomplish this. Whilst this may be feasibel for a fairly small site I don't see how this solution would hold up for a large site (with serveral hundred concurrent requests to anyone of several thousand pages). The problems/questions I can see are: As a single textfile is used, when there are several thousand entries it will become difficult to manage. Can updates be made, during operation, to the content ? What happens if a user requests the files content while it is being edited ? Is the textfile cached for performance, or will concurrent calls compete for the same file-resource ? As I'm probably not the first person who is trying to use Struts on a larger scale for internationalization issues I thought someone might have a better solution. Suggestions ? //Linus Nikander - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
