I tried to run multiple cassandra daemons on the same host, using different ports, for a test env.
I thought this would work, but it turns out that the StoragePort used by outputTcpConnection is always assumed to be the one specified in .yaml, i.e. the code assumes that the storageport is same everywhere. in fact this assumption seems deeply held in many places in the code, so it's a bit difficult to refactor it , for example by substituting InetAddress with InetSocketAddress. I am just wondering, do you see any other value to a custom storageport, besides testing? if there is real value, maybe someone more familiar with the code could do the refactoring Thanks yang
