I think that it won't help us to create unit tests for the JVM ;-)
A similar test would not prevent us from using again InetAddress the
wrong way, so we don't need it.
If Noel investigated on it and made sure that we misused the InetAddress
cache it is enough for me: we *misused* the InetAddress and probably
this happened because of a really bad default in the JVM.
This test imho would give us the same improvement we could get from a
test that put objects into a LinkedList until an OOM is thrown: none but
proving that the JVM has the OOM exception and that the LinkedList uses
strong references.
Stefano
Noel J. Bergman wrote:
Jürgen Hoffmann wrote:
I do not know if it is possible to fake a remote IP while doing local
connections within Java
We have a full class A subnet (127/8) to play with. We cannot do the
network configuration portably, nor in Java, but we could:
loop x:
loop y:
loop z:
UNIX: assign lo:0 to 127.x.y.z
Java: connect from 127.x.y.z (lo:0) to localhost (lo)
endloop
endloop
endloop
We'd also need a DNS server (or just /etc/hosts) to provide a unique name
for each IP. I don't know if this is still high on anyone's priority list,
but that's as simple a solution as I've come up with so far.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
