[DP-59] Issues with IPv4 vs IPv6 on OSX

[Imported from JIRA. Reported by rodlogic @rodlogic) as DP-59 on 2012-08-18 15:47:24]
It seems that the current implementation doesnt like IPv4 when binding the server and it doesnt like IPv6 when connecting from a client.

Using distributed-process v0.3.1 installed with cabal install.

Starting the server using IPv4 (DOESNT WORK):

Workstation :: ~DEV » runhaskell Server.hs 127.0.0.1 12493
Bind to 127.0.0.1:12493
Server.hs: bind: unsupported operation (Can't assign requested address)

Starting the server using IPv6 (WORKS):

Workstation :: ~DEV » runhaskell Server.hs ::ffff:127.0.0.1 12493
Bind to ::ffff:127.0.0.1:12493
Echo server started at ::ffff:127.0.0.1:12493:0

Running the client using IPv4 (WORKS):

Workstation :: ~DEV » runhaskell Client.hs ::ffff:127.0.0.1 11111 127.0.0.1:12493:0
ConnectionOpened 1024 ReliableOrdered 127.0.0.1:12493:0
Received 1024 ["Hello world"]
ConnectionClosed 1024

Running the client using IPv6 (DOESNT WORK):

Workstation :: ~DEV » runhaskell Client.hs ::ffff:127.0.0.1 11111 ::ffff:127.0.0.1:12493:0
Client.hs: Error connecting: TransportError ConnectFailed "user error (Could not parse)"

Start with the Server.hs and Client.hs command lines in the report and reproduce the IPv4 bind and IPv6 connection failures on OSX. Trace the distributed-process transport and address handling involved in binding and connecting; done means the reported IPv4 and IPv6 scenarios work without these errors.