>> There are probably tons of howtos that uses 127.0.0.1, so that will >> break windows port. > > If some less-than-accurate howto used literal address instead of > "localhost", it doesn't mean anything. If some documentation is not > part of the project, then why should we care? I can't say it can > "break windows port" anyhow. Also, aren't all those older MS systems > declared EOL already (only limited "extended support" etc)?
Can newer Windows versions map IPv4 into IPv6? Last I tried using .NET on windows 7, I could not create a single socket that could listen on both IPv4 and IPv6. We would probably get some less whining and support questions if support both IPv4 and IPv6 transparently which most IPv6 ready software tries to do. Stian ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
