Hi alberto,
>> 1- I dont have GPF reporter but can compile the example without problem, is this ok?
yes, it will compile and run ok. The big problem though is that if _any_ DLL causes a GPF on load then the whole server comes down. With GPFReporter the server will immediately restart itself (and disable the offending DLL.)
So without GPF Reporter you may want to use an external service to restart the server if it goes down.
>> 2 - In the doc pdf you can read:
" This technique does not work for secure sites, because with a secure site the host name is encrypted."
this statement is obsolete. Support for multiple domains (via "Site Name Indication (SNI)" was added (and became popular) since that doc was written.
>> Is there an updated doc of multi host?
Are you reading the PDF? No I don't think that doc has been updated.
>> 3- What does Propagate Delete session PDS means?
The WebServer (ie Host Exe in this case) is in charge of cleaning up sessions. But you may have code in your DLL which is needed when cleaning sessions. (In WebHandler, NotifyDeleteSession method.) So the Propagate means that the call to delete sessions is being passed down to the WebHandler in the DLL.
>> 4- Only way of testing the sites is using the Host windows file to redirect them to the host IP.
It's not the "only" way, but yes, it's usually the simplest way (unless you have quite a fancy router.)
>> (you cant use ports in the host file IPs),
correct. (and you don't need to - if you are running locally on port 88 then just direct to port 88.
For example, in your hosts file you might set
www.capesoft.com 127.0.0.1
Then in your browser go to
http://capesoft.com:88Then in your "site list" of expected domains you would be looking for capesoft.com:88
(I think. going from memory. try it and see)
>> changing the host IP to 80 from 88 works ok but in the Notes tab it still says host is in port 88.
Then you probably didn't change it in the right place. Where did you change it?
cheers
Bruce