The sdk should auto-detect ipv4 loopback and ipv6 loopback for daprd communication.

[LMWF]

Expected Behavior

Today the sdk will choose the ipv4 loopback address to contact darpd: 127.0.0.1 (this was changed from "localhost" today). Some users may prefer ipv6 or may operate in an ipv6 only environment. The sdk should automatically detect which one to use: ipv6 or ipv4.

Actual Behavior

Today the sdk will always use the ipv4 loopback address: 127.0.0.1 to connect to daprd.

[yaron2]

Might be better to detect the environment automatically and set the address accordingly. This is a detail the user shouldn't be aware of.

[amanbha]

While reducing the friction because of issues faced by localhost is good. Asking user to provide this ipv4(or ipv6)address is not good solution,
I agree it should be auto discovered for user.

[artursouza]

@amanbha @yaron2 I agree for auto-detection. It would be interesting to see how the auto-detection can be done without causing delay (waiting for IPV6 connection to fail, for example).

[yaron2]

A delay on startup is a non-issue.

[artursouza]

@yaron2 If it is "small", I agree.

[yaron2]

Looks like Java has this built in: https://docs.oracle.com/javase/7/docs/api/java/net/InetAddress.html#getLoopbackAddress%28%29

[LMWF]

Doesn't it have to use the one daprd is using? Can't daprd be using the ipv6 loopback, and that api returns the ipv4 loopback?

[artursouza]

I thought about it too. If both are present, client must use what dapr is using - which can only be known by trying to connect.