Locating the Server

The HyperGate server acts as an intermediary between HyperGate clients and existing web servers.  In normal operations, you will need to install and run a copy of HGserver on or near each web server that you wish to work with HyperGate.  The simplest strategy is to run HGserver on the same CPU as the web server.  This involves the least configuration and typically provides the best performance.

See the Relay section for instructions on using HyperGate to accelerate a single network segment.

In some cases, it may be desirable for HGserver to run on a different CPU than the web server.  For example, if the web server has limited resources, or if one or more web servers is located behind a firewall.  HGserver may be installed on any CPU with direct network access to the target web server.  For maximum performance, the network connection between the two should be faster than that of the WAN connection and the latency (ping time) between them should be no more than a few milliseconds. 

To simplify HyperGate URLs and client configuration, the HGserver can be given the name of web server it is targeting by using the “-h” option or the “Host” configuration variable.

See the Installation section and the README file for details on how to install the server software.  See the HGserver chapter for information on configuring the server software.