Default Rover Sessions

The ~/.rover-session-init file specifies a set of mappings for service names. Each service name is mapped to a set of servers, each of which has a path to use (when using the forked server) and an optional limit on the number of simultaneous outstanding connections (to prevent server overload). The file has the following format:


	ServiceName
	Server1 Path1 ConnectionLimit1
	Server2 Path2 ConnectionLimit2
	   :	  :	  :
	Servern Pathn ConnectionLimitn

Cut and paste the following session mapping table into ~/.rover-session-init to initialize rover session mappings.

Notes:

To contact a server using a port other than the standard HTTP port (80), use normal URL syntax (e.g., rover.lcs.mit.edu:9090).
The following mapping table assumes a standalone Rover server at port 9090. To use the forked Rover server, replace the 9090 port specifiers with the httpd server's port.
For a server on the same machine as the client, specify the RoverServer as localhost , instead of using the machine name. Using the machine's name may cause problems when disconnected.

.rover-session-init File

appl
RoverServer:9090 /cgi-bin/rover/nph-rover 5

e-mail
RoverServer:9090 /cgi-bin/rover/nph-rover 5

http
RoverServer:9090 /cgi-bin/rover/nph-rover 5

ical
RoverServer:9090 /cgi-bin/rover/nph-rover 5

irolo
RoverServer:9090 /cgi-bin/rover/nph-rover 5

rfs
RoverServer:9090 /cgi-bin/rover/nph-rover 5

smtp
RoverServer:9090 webserv 5

tcl/tk
RoverServer:9090 /cgi-bin/rover/nph-rover 5

tclIndex
RoverServer:9090 /cgi-bin/rover/nph-rover 5

time
RoverServer:9090 /cgi-bin/rover/nph-rover 5

webcal
RoverServer:9090 /cgi-bin/rover/nph-rover 1