The article consists of four iterations, which are all working examples. These are
1. Simple chat (Samples\SimpleChat folder).
2. User-friendly chat (Samples\UserFriendlyChat folder).
3. Registrable chat (Samples\RegistrableChat folder).
4. Palace chat (Samples\PalaceChat folder).
All listed types of chat have similar IIS installation process. In IIS administration panel need to define virtual directories for required types of chat. Point them to appropriate disk location for the sample, with addition �\XMLChat� subfolder. For simple chat it can be as following:
Virtual Directory name: SimpleChat
Content Directory: <Your local path>\Samples\SimpleChat\XMLChat\
Access permission can be default: Read and Run scripts. Session state should be disabled for better performance.
Registrable chat and Palace chat also require folder with read-write permissions. It can DB folder, which not a subfolder of Web application. For example: <Your local path>\Samples\SimpleChat\DB\
After these steps completed, it is ready for browsing and trying to chat. If something wrong, try to install MS XML Parser 3.0 or higher on server side. It is also shipped with IE 5.0 and later.
The chat settings can be customized in INC/Settings.js file. Here provided a set of functions to customizable.
getMessageRefreshTime() � specifies amount of time, in seconds, for next messages history pane refresh.
getVisitorsRefreshTime() � same as previous, but for active users pane.
getSessionExpirationTime() � specifies time-out interval of disconnected user expiration, in seconds.
getMaxMessages() � specifies maximum quantity of messages to represent for users.
getUsersDataPath() � specifies disk location to store persistent users information.
getRoomsDataPath() � same as previous, but for storing rooms information.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.