The Architecture
Server-side Overview

S-IMCO's IM System architecture consists of Dispatch Server, Status Server, IM Server and a Windows & Wed based (php) administration consoles. The system uses MySQL as a database. You can download an evaluation copy today.

Requirements

• Pentium || - 450Mhz
• 256 MB RAM (512 recommended)
• 30 MB hard disk space
• Windows 2000, 2003, XP

Security
S-IMCO's all the three server support TLSV1, SSLV3, SSLV2 (not recommended). The system uses the industry standard TLS/SSL tool-kit OpenSSL for that purpose. Different TLS/SSL protocol versions can be set via Windows or Web-based Administration Consoles.

Administration Console
S-IMCO's IM System can be easily administered via two types of administration consoles.

1. Windows Based Administration Console.
2. Web-based Administration Console.

Dispatch Server
The Dispatch Server redirects the user to the appropriate Status Server. With the users first connecting to dispatch server before being redirected, gives the system ability to seamlessly redirect the users to a different Status Server, incase of a original Status Server not being available. Stopping the Dispatch server will not allow any new users to login to the system, but the users already logged-in, will remain connected without noticing any difference.

Status Server
Status Server is the most critical part of S-IMCO's IM Architecture. Status Server authenticates the user, maintains the user status and user lists and updates other users about any changes. Status Server also stores and sends some of the user information e.g. Friendly Name, Personal Message, and Privacy options. Stopping Status server will logout all the users logged-in to the IM System.

IM Server
IM Server hosts all the public and private chat-sessions, as well as secure File and Avatar Transfer. Stopping the IM Server will close all the already opened chat-sessions, and will not allow the logged in users to start any new public or private chat-sessions.