Hi Noel. See below...
Kind regards Juergen Von: Noel J. Bergman [mailto:[EMAIL PROTECTED] Jürgen Hoffmann wrote: > I think Testing is very important. So do I. That's why I added run-unit-tests to the dist target. And why I added support for running specific tests during development --- so that they would be run because it is convenient to do so, rather than skipped because running them is onerous. [JH>] this is a good solution. > I personally dislike partial testing, because you might miss certain > areas of the code which were affected by a change As you might have noticed from my discussion with Danny, I agree. That's why a dist build includes a clean first and a full run of the test suite. And why I expressed concern about relying on partial tests based upon presumed dependencies. [JH>] I did not, sorry. But now this is clear to me. > 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. [JH>] Feasible enough. Do others have an idea on how we could test this particular leakage automatically? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
