Client

Many libraries have existing networks within their institutions. Consequently, existing PCs are available to use as clients for an Intranet. There are three areas that one must consider to ensure successful Intranet implementation; compatibility, capability, and capacity. Compatibility is a software issue that refers to the ability of the operating system to work with an application. Therefore, the system has to provide support for TCP/IP and be able to run the browser selected for the library environment. Capability is the PCs ability to run the client software selected (browser). Capacity refers to the hardware of the client . The two areas to focus on are the amount of memory available and the size of the hard drive. If the PC has already been in use on the library's network for some time then it is unlikely that it will meet the requirements for successful Intranet support. Basic Intranet applications in conjunction with other applications can put too much of a load on the machine and cause it to not operate properly. Intranet technology is based on the TCPI/IP communication standard: setting up an Intranet means adding TCP/IP and HTTP to the library's network. Putting the TCP/IP suite on the desktop requires a stack of network layers which will load down the PCs capacity. An alternative to installing each client with the TCP/IP suite is to use a server side gateway that leaves the client configuration unchanged except for the addition of a vendor supplied driver. Either way, the increased graphics and database applications will determine any additional PC hardware requirements.

Factors in client selection and sizing

CPU? / Memory? / Hard drive?
Operating System (OS)
Types of applications
Number of applications

(Wesley & Wesley, 1996, 92)

Contents

Table of Contents

Part 1: Intranets Philosophy Structure Part 2: Intranet Installation Basic Network Configuration Server Client Publishing Applications Security Conclusion References