×
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.
Change: , like TCP/IP.
To: , like http.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Tuesday, May 28, 2019 11:23 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Why adulterate ports vs using an additional IP address? Was: Ports IP specific?
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?
Rob Berendt
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
