entry, I mentioned that I had reimplemented the RMI
registry portably, before discovering that there was a much
simpler solution to the security problem I was addressing.
Here's the reimplementation for what it's worth.
If you've had occasion to use the RMI registry seriously, you
may have encountered some of its shortcomings. Chief of these
is that anybody on the local machine can modify the registry.
There are only a few things you can do about that, of which the
craziest is to reimplement enough of RMI to code your own
compatible version of the registry.
A multihomed computer is one that has more than one
network interface. Problems arise when you export an RMI object
from such a computer. Here's why, and some ways you can work
around the problem.
I'm writing this in what I used to think was the world's
where I have a five-hour stopover. I'm somewhat revising my
opinion of the airport because I discovered a "Quiet Seating Area"
with real seats and real quiet. A bit like a business-class
lounge but for the plebs.
I'm at The Spring
Experience 2006 in Hollywood, Florida (between Miami and Fort
Lauderdale) where I've been invited to speak.
I recently wanted to add some performance measurements to an
application. To avoid duplicating code everywhere I needed to
make measurements, I coded up a small helper class.
Defining an equals(Object) method in a public class is not
always straightforward. One reason it might not be is that the
answer to the question "are these objects equal?" might be
An inadvertent change in JDK 6 means that MBean attributes and
operations no longer appear in the order they were in a Standard
MBean interface. I wanted to fix this, but now I'm not so sure.
Here's the background. Suppose you have a Standard MBean with
The JMX API includes the possibility to create "Dynamic
MBeans", whose management interface is determined at run time.
When might that be useful? Here's an example.