This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Jeff Sturm wrote:
On 4 Jun 2002, Tom Tromey wrote:ResouceBundles should definately be cached - I'm pretty sure we do it and the spec suggests this behaviour:
Bryce> Presumably it would be reasonable to cache negative results for
Bryce> resource bundle (and class?) lookups. People don't expect to be
Bryce> able to dynamically add new resource bundles to a running
Bryce> application, right?
I wonder. Maybe someone could test the JDK and see what it does. You
could imagine wanting to dynamically add resource bundles to some
long-running application like a web server -- it isn't a completely
absurd idea.
My thoughts: - Dynamically replacing locale data or other system bundles isn't likely to happen, so Per's suggestion of caching the default locale bundle is a good idea.
So the decision to cache the resource might best be left with theI agree and I suspect that this is the way things work in the JDK. I'll try to confirm this before we start hacking it, though.
classloader, and the system classloader might as well cache its results
forever. (Mine's a pragmatic view not necessarily based on fact, but on
real experience with sometimes ill-behaved web applications.)
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |