support both HTTP and HTTPS communications?
Speed and simplicity. If you are building a high-volume system where every tenth of a second counts, then the overhead of HTTPS communications can start to add up. HTTPS adds computational overhead as well as network overhead. HTTPS can also be more complex to set-up. You need to purchase a secure certificate and also give the server where Trevance is installed a fixed domain name since certificates are tied to the name of the machine. There are several server configurations where HTTP can be perfectly acceptable. 1. Connect the Trevance® server and your public server on their own private network that is stored in a physically secured location. 2. Run a Virtual Private Network (VPN) between your public web server and the Trevance® server. This builds a secure, encrypted channel between the two machines. HTTP communicating over an encrypted VPN will be quicker than HTTPS. With HTTPS, every request requires the overhead of a ‘handshake’ between the two machines. With an encrypted VPN, th
