12-08-2018, 05:24 PM
Hi there. Thank you so much for your comments. I really appreciate them. I flipped my SA Server over to this new concept and it worked for the server on port 8888. When I update to what you have here, there is a conflict since the root domain is IIS and the subdomain is what I am trying to map. Looks like there is no way to have part IIS and part SA Server. I happened to have a domain that I was not using in IIS so I deleted from there and then set in SA Server and all worked with port 80.
For testing where I have no domain landing do I just set the bound IP to the server IP and then have port 8888? The following is what I had working last night for the recipe but I thought I would ask:
BoundIP=server IP
AddDefaultBind := false;
HostWildcard := hwWeak;
VirtualHostName := '';
Port=8888;
Also in IIS, I can replace a file and then it manages itself to reload and the user can just have a session reset worst case and keep working. Here I have to down the service, replace the exe and then start again causing major disruptions. How do you at least put up a under construction page while the system is down? Would I have another slim under construction exe and then start that capturing the port or domain as appropriate and then bring down the primary exe so traffic routes now to the under construction?
After contemplation, I have abandoned the dll concept sine this will be the same under construction issue anyway and who wants to be nested in IIS for another point of failure. The power of Delphi and IW is to keep out of Microsoft Tech as much as possible.
One last question is the threads per core setting. In production, I am assuming this is unlimited, right?
Cheers.
bob
For testing where I have no domain landing do I just set the bound IP to the server IP and then have port 8888? The following is what I had working last night for the recipe but I thought I would ask:
BoundIP=server IP
AddDefaultBind := false;
HostWildcard := hwWeak;
VirtualHostName := '';
Port=8888;
Also in IIS, I can replace a file and then it manages itself to reload and the user can just have a session reset worst case and keep working. Here I have to down the service, replace the exe and then start again causing major disruptions. How do you at least put up a under construction page while the system is down? Would I have another slim under construction exe and then start that capturing the port or domain as appropriate and then bring down the primary exe so traffic routes now to the under construction?
After contemplation, I have abandoned the dll concept sine this will be the same under construction issue anyway and who wants to be nested in IIS for another point of failure. The power of Delphi and IW is to keep out of Microsoft Tech as much as possible.
One last question is the threads per core setting. In production, I am assuming this is unlimited, right?
Cheers.
bob