
20 Jul
2011
20 Jul
'11
12:39 a.m.
No, this is not intentional behavior. I just borrowed the code for bindPort from elsewhere. If you have a better implementation, I'd be happy to pull it. But I think that at least until the network package change happens we should conditionally compile to make sure Warp always listens on IPv4 by default.
OK. Here is a patch. Please fetch it at your own convenience. https://github.com/kazu-yamamoto/warp/commit/02c1396c86e3fceb48cbe7df58cb631... I'm using runSettingsSocket with my own dual-stack socket. So, I can wait. --Kazu