There are several network settings that you can modify to better make Quid Pro Quo fit your needs. Quid Pro Quo allows you to change the number of threads listening for incoming connections, the TCP port on which listens for connections, the buffer size for outgoing data, and the amount of time which Quid Pro Quo cedes to other applications.
To configure your server's network settings, select "Configure Server..." from the Control menu. You will be presented with a number of options, the first of which is the TCP Settings.
Interval: The Multitasking/Interval controls how often Quid Pro Quo yields time to other applications. The higher the position of the slider, the less time that applications other than Quid Pro Quo will receive. Having this set high can greatly improve connection processing speed when server load is heavy. However, this comes at significant cost to other applications, including CGIs running with Quid Pro Quo. The Quid Pro Quo application also becomes very sluggish vis-a-vis user input (such as in the Configure dialog) when this is set high and there is a heavy load. Under a loght load, this setting has a negligible effect. You should experiment to find the optimum setting for your site.
Sleep: The Multitasking/Sleep option allows you to control Quid Pro Quo's "sleep" time. This is the amount of time that other applications will be given to run while Quid Pro Quo is the foreground application. The higher the slider position, the less time that other applications are given to run. In real terms, the range of the slider control is 0 to 60 ticks. If Quid Pro Quo is the only application you intend to run on your server (no CGI applications, either), feel free to set this all the way to the top. If you run other servers, or will be using CGI applications, you should experiment to find the optimal setting for your conditions.
This is the TCP port on which this copy of Quid Pro Quo will listen for incoming connections. The "well-known port" for HTTP is 80, and this is the default for Quid Pro Quo. Port 80 is the port that web clients will attempt to connect to when an explicit port number is not specified. When using a port other than 80, clients must specify the port in their URL request. For instance, if your server is listening on port 3000, a URL for your site would appear as
When you change the port that Quid Pro Quo is using, you must quit and restart your server for the changes to take effect.
Max Connections determines the number of connection threads that Quid Pro Quo creates at startup. The more threads that are created, the more simultaneous connections that Quid Pro Quo can service. However, increasing the number of connections also increases the server's memory requirements. Quid Pro Quo needs at least one megabyte plus 64 kilobytes per connection. The use server side includes and cached files eat up more memory. Setting the Max Connections value too high can adversely affect server performance. If you create more threads than your hardware can handle, server slowdowns or even deadlock can result. It should take some experimentation to find the optimal number of connections. The default is 18, a number which all PowerMacs should be able to handle with aplomb. Some less capable 68K Macintoshes may have trouble with this many connections. When you change the Max Connections parameter, you must quit and restart your server for the changes to take effect.
The TCP buffer size is the amount of data that Quid Pro Quo will spool up before sending it to the client. You should set this value based on the speed of the connection that your clients will be using to connect to your site. A larger buffer will favor fast clients, while a smaller buffer favors slower clients. Experiment with this setting: clients connecting via modem links will probably work best at a setting between 1024 and 2048, while clients with dedicated connections could use a setting between 4096 and 8192. The default value is 4096.
This value is the time, measured in seconds, that Quid Pro Quo will wait for slow clients and CGI applications before giving up on them. The default value is 60 seconds, which is a reasonably generous setting. If your site is unusually busy, you might want to set this number lower to free up errant connections more quickly. Be sure to leave the setting high enough so that slow clients won't be summarily disconnected while transferring data.
When this box is checked, Quid Pro Quo will look up the domain name of all clients connecting to your site. This is useful for logging purposes: clients will be logged by their domain names rather than their more cryptic IP addresses. DNS lookups can have an adverse effect on performance, however. Looking up each address forces a connection to wait for a name lookup to finish before it can serve the next incoming connection. If you have a busy server, you should leave this option unchecked. If you have an Allow/Deny address configured with a domain name, Quid Pro Quo will do a domain name lookup regardless of the value of this checkbox. If you have a heavily loaded site, you should consider leaving this setting off. If you require domain names rather than IP addresses in your log file, most log file analysis tools will do domain name lookups on the IP addresses recorded in the logfile, negating the need for Quid Pro Quo to perform this task.
Welcome | Contents | Glossary