pass the application, locale/style/variation into your thread and use
application.getlocalizer() to do the localization.
-igor
On Wed, Feb 10, 2010 at 3:08 AM, Matthias Keller
wrote:
> Hi
>
> We have a complex application which needs to calculate some very expensive
> things. Those could easily
I guess you could safely share your IStringResourceLoaders, as they
are already shared
between multiple session (and thus potentially multiple threads).
If you really need to share the Session object between threads, you have
to roll some kind of locking. What I've done in the past is adding a
Reen
About share your application IStringResourceLoader objects with your thread
?
On Wed, Feb 10, 2010 at 9:25 AM, Matthias Keller
wrote:
> Hi Ernesto
>
> Thanks for your reply. This would basically be possible but very
> complicated because the threads need dozens to hundreds of values, so it
> woul
Hi Ernesto
Thanks for your reply. This would basically be possible but very
complicated because the threads need dozens to hundreds of values, so it
would be a very tedious and complicated task to collect everything in
advance just to pass it to those threads.
Matt
On 2010-02-10 12:18, Erne
Why not just "collect" the information you need and pass it to the thread?
Can't you know in advance which localized values you are going to need?
Best,
Ernesto
On Wed, Feb 10, 2010 at 12:08 PM, Matthias Keller
wrote:
> Hi
>
> We have a complex application which needs to calculate some very ex
Hi
We have a complex application which needs to calculate some very
expensive things. Those could easily be parallelized so we thought about
having a thread pool to do that.
Unfortunately, that code needs access to the localizer and the
application (for some configuration values) so we're sett