03-22-2018, 02:19 AM
My requirements are
1. NO IIS. You keep saying over and over that I can use IIS, and I have said 2x at least that I do not have the option of IIS. So I will say it again, I NEED A SOLUTION THAT DOES NOT USE IIS.
2. The computer needs to have only a single IP address
3. I need to have multiple applications listening on port 80.
You keep saying HTTP.SYS is not required, and I can use IIS, even though I have said over and over that I do not want to use IIS for this application
As far as I have read, HTTP.SYS is the only thing that would allow ALL of the above requirements to be fulfilled.
It is a shame that if I want to deploy multiple Intraweb applications on the same computer, listening to the same IP address, bound to the same port, that I need to use IIS. It would be very convenient if I could deploy multiple IW applications as windows services, all of them listening to port 80, without requiring multiple IP addresses.
If you could create a "project type" that plugged an intraweb app directly into HTTP.SYS that could deploy as a windows service, that would satisfy these requirements.
If you tell me to use IIS again, my brain may explode
1. NO IIS. You keep saying over and over that I can use IIS, and I have said 2x at least that I do not have the option of IIS. So I will say it again, I NEED A SOLUTION THAT DOES NOT USE IIS.
2. The computer needs to have only a single IP address
3. I need to have multiple applications listening on port 80.
You keep saying HTTP.SYS is not required, and I can use IIS, even though I have said over and over that I do not want to use IIS for this application
As far as I have read, HTTP.SYS is the only thing that would allow ALL of the above requirements to be fulfilled.
It is a shame that if I want to deploy multiple Intraweb applications on the same computer, listening to the same IP address, bound to the same port, that I need to use IIS. It would be very convenient if I could deploy multiple IW applications as windows services, all of them listening to port 80, without requiring multiple IP addresses.
If you could create a "project type" that plugged an intraweb app directly into HTTP.SYS that could deploy as a windows service, that would satisfy these requirements.
If you tell me to use IIS again, my brain may explode