Originally posted by Ulf Dittmer:
That's a good point - using a class file hierarchy instead of a jar file would circumvent this particular problem.
Originally posted by Ulf Dittmer:
...
So, from a security standpoint, the cache doesn't make anything worse than it already is.
Originally posted by Ulf Dittmer:
Applet jar files are cached, and remain somewhere on the hard disk. The location and size of the jar cache can be adjusted with the Java Plugin control panel.
Originally posted by Jim Yingst:
Of the Java techniques listed, cloning and deserializing are the only two which do not ultimately invoke any constructor. In that sense, we may say that there are just three ways to create an object in Java:
(1) The messages are not distributed by a load balancer, but by an internal queue-to-queue mechanism through the queue managers themselves. When CLIENT_A talks to its queue manager an exit will choose which of the actual "queue instances" to put the message on.
(2) CLIENT_B just connects up to the clustered queue the same way it would connect to a local queue. The redbook I referred you to has some detailed examples of how this works.