On 08/26/2008 09:20 AM, Christopher Hegarty - Sun Microsystems Ireland wrote:
On 08/26/08 14:41, David M. Lloyd wrote:
On 08/20/2008 04:37 AM, Alan Bateman wrote:
FWIW, a while back I prototyped an "in tree" solution for
SocketChannel. The primary motive was to allow for Sockets Direct
Protocol (which uses IP addressing) and Unix Domain Sockets (which
required a new SocketAddress type).
I disagree here. Just because C has traditionally used struct
sockaddr in an overloaded fashion doesn't mean it's a good idea to
mirror this on the Java side.
Sorry David, I'm sure what you mean here. Can you please clarify.
I just mean, what would be the benefit of using SocketAddress rather than
using a String or Path directly? You can avoid the difficulties of
extending SocketAddress by simply not using it.
- DML
