tags:

views:

15

answers:

1

I am developing a web application that relies heavily on Applets. Some third party code causes several, in some cases hundreds of, remote lookups of classes and some other resources from the server. This results in a significant performance issue. I've built my own code such that if something is NOT found within the .jar, it is not needed.

Does anyone know of a decent way to prevent the remote lookups (besides making sure all the stuff I see in my access logs is actually in the .jar)?

+1  A: 

Try experimenting with the codebase_lookup parameter mentioned in Special Applet Attributes.

Andrew Thompson
Thanks a lot, this solved it beautifully!
Lauri Lehtinen