What problems I'll get if I will fix the network port my application is
listening?
I observe this behviour from very famous projects. For example apache and
nginx, they both by default trying to listen port 80 and if it's already
occupied then they just fail to start and need to be reconfigured.
What if for my small server project I pick some port not mentioned on List
of port numbers yet? My goal is to make the server application working at
most of households with wi-fi routers. They usually don't have any unusual
ports occupied (or they do?). So if I occupy the one I shouldn't have
problems most of the time. Am I wrong? What problems I might get with this
approach?
No comments:
Post a Comment