Since the example / demos used port 2003 for the REST server, I carried on using it.
I am trying to use Certify The Web to auto renew the certificate. It only binds it to port 443. I have to manually bind it to 2003, when the Client complains. Its not ideal.
A solution is to use port 443 for the REST server as well.
Is there a reason for using a different port?
Reason is many applications don't share the URL in a single port like TMS Sparkle does. Most applications "take over" the TCP port, for example, if you run an Indy server on port 80, no other application in the computer will be able to listen to that port.
Thus, use use a different port by default so developers could easily run and debug the Sparkle servers right away with a low chance of conflict. If we used something like port 80 or 443 it will be very likely that developers would have to change it to properly run and debug in their dev machines.
As as a correction, the default port is 2001, not 2003.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.