3 ms·
Yep. It's rather useful too. If you're simultaneously testing multiple services that expect to exclusively bind to a socket, you can set application a to listen
by Sanddancer 12y ago
Yep. It's rather useful too. If you're simultaneously testing multiple services that expect to exclusively bind to a socket, you can set application a to listen on 127.0.0.1, and application b to 127.127.127.127. Beats stopping and restarting by a long shot.
Offhand, the BitTorrent Sync WebUI thing has a rather bad smell to it. There are ways to protect that info from getting out, but it's definitely suspect.
- yuvipanda 12y agoCan't the services just listen on different ports?
- Sanddancer 12y agoFor a lot of cases, yes. For cases of things like DNS resolvers, no. There's too much stuff that requires a specific port.