On Fri, Aug 14, 2009 at 9:19 PM, Schwab,Wilhelm K<bschwab@anest.ufl.edu> wrote:
SocketAddress>>printOn: looks like it does some questionable things, but I am fuzzy on what exactly is happening and what should be done about it. Â My thought would be that the address should have name and number aspects, that resolving would do the respective lookups, and that inspecting should not attempt the lookups. Â Do you agree? Â How broken is the implementation?
I cant' say that I am thrilled about addresses being inherited from ByteArray - I suppose it can happily be the address and have an iv for the name, but what if one knows the name and later wants to resolve the number? Â This sounds like a job for a subclass of Object with named variables. Â Anybody agree or disagree?
I saw some problems which appeared while printing a socket address on Windows (primitive has failed). So, cleaning that would be cool, thank you. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry