|Table of Contents|
The VolanoChat server is actually three servers in one, as shown in Figure 4.1 below.
Figure 1: VolanoChat server component architecture.
The Servlet Runner
The Servlet Runner runs on port 8080 by default. VolanoChat now ships with the Apache Tomcat 4.0 servlet runner, replacing the embedded Sun JSDK 2.0 servlet runner included in previous versions. The servlet runner accepts HTTP requests for Java servlets and sends back their HTTP responses. The server properties:
servlet.port=8080 servlet.minprocessors=5 servlet.maxprocessors=20
replace the earlier servlet runner configuration file defined by
The Tomcat HTTP request access logging is enabled and defined by the properties:
The Administrative Server
The Administrative Server runs on port 8001 by default. The administrative server accepts network connections from the
COM.volano.Shutdown Java applications when given the correct administrator password.
The Chat Server
The Chat Server runs on port 8000 by default. The chat server accepts network connections from the
COM.volano.MyVolanoChat Java applets and delivers chat messages between all connected clients.
The chat server reads its configuration from the
/conf/properties.txt Java property file, its list of permanent rooms from the
/conf/rooms.txt file, and its access control directives from the following files:
hosts-allow.txt hosts-deny.txt referrers-allow.txt referrers-deny.txt
The chat server writes access records to the following default files, where yyyy-mm-dd is the current year, month, and date:
access-yyyy-mm-dd.log error-yyyy-mm-dd.log public-yyyy-mm-dd.log private-yyyy-mm-dd.log banned-yyyy-mm-dd.log servlet-yyyy-mm-dd.log http-yyyy-mm-dd.log velocity-yyyy-mm-dd.log
These files replace the following obsolete files:
access.log error.log public.log private.log
The chat server sends HTTP GET requests for the membership CGI script in order to verify member names and passwords.
|XHTML 1.0||Table of Contents|