This is the mail archive of the java-patches@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]

Re: Patch: RFC: PR 9125


>>>>> "Oscar" == Oscar Pearce <oscar@pearceenterprises.com> writes:

Oscar> I was thinking about this (for what little that's worth) and
Oscar> I'm not sure that this'll come up in practice.  If you're
Oscar> redeploying a webapp (for instance), you would expect the app
Oscar> server to create a new ClassLoader to serve the newly deployed
Oscar> webapp.

We could go around modifying the various programs to search for the
.so file first and use the (new) solib: URL stuff.

Oscar> Actually, thinking about it a little more, wouldn't it make
Oscar> more sense to cache only successfully loaded .so files?

Our system class loader will look for .so files.  If we don't cache
the failures then we can end up making a lot of dlopen() calls that
just fail.  Apparently this can cause performance problems.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]