× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Tue, May 28, 2019 at 10:23 AM Rob Berendt <rob@xxxxxxxxx> wrote:
I hear of people using off the wall ports to support multiple listeners. I'm not talking about anything difficult to bind specific, I'm just referring to the easy stuff, like TCP/IP.
Why would anyone set up a web server on port 80, another one on port xx, another one on port yy, etc? Instead, why not just supply multiple IP addresses to the box? Doesn't using multiple port numbers like this cause one to either use some redirects, or have the end user have to specify the port in the url, like http://myserver.com:xx?
Is it because it appears to be a drudgery to talk to the network guy and get another IP address? Or why else?

A few reasons come to mind ...

1. Listening on a different port is a lot easier than reconfiguring
the system to have an additional IP address.
2. If the port is higher than 1024, you don't need to be a privileged
user to bind to the port.
3. If your network guys decide to reconfigure the network and assign
new IP's, there are fewer addresses to change.

david




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.