|
As the
pioneer in interoperable instant messenger and presence
management, Geodesic offers a reliable and robust Instant
Messaging platform available for small and large portals
and corporates. The Instant Messaging solution offered
by Geodesic encompasses both client-side and server-side
technologies.
|
| |
| Client
Architecture |
 |
|
The instant
messaging client is based on "Mundu Interoperable Instant
Messaging (MiIM)" and has been developed using MFC and
ATL COM technologies. The instant messaging client comprises
three different layers.
|
| |
The User Interface Layer |
|
|
The user
interface layer consists of all the controls and actionable
items. It is the part of the application that is visible
to the user. The interactions of the user with the application
happen via this layer.
|
| |
|
The Service layer |
|
|
The Service
Layer allows communication between the user interface
layer and the component layer. The service layer provides
a consistent mapping between the user interface and
various service components.
|
| |
|
The Component layer |
|
|
The component
layer presently comprises five instant messaging service
components (one for each instant messaging service viz.
Mundu, AIM, ICQ, MSN and Yahoo), and can be scaled horizontally
to include more instant messaging services in the future,
without affecting the existing structure. Respective
components perform all tasks pertaining to a particular
instant messaging service and use a proprietary communication
layer that allows communication over different kinds
of Internet connections.
|
| |
| Server
Architecture |
|
|
The Mundu
Messaging Service is designed to be robust and scaleable.
The architecture is structured in a manner that it is
simple for licensees to deploy the server software over
one or multiple systems. Licensees can start with smaller
configuration and grow to a medium or a large configuration
by adding more servers, network equipment and resources
viz. CPU's, Memory etc. The instant messaging server
system ensures optimum performance as the architecture
is broken down into components that have individual
tasks.
|
| |
|
Support Server |
|
|
The Support
Server provides for authentication, contact List management,
upgrades, bug fixes and domain information.
|
| |
|
Init Server |
|
|
The Init
Server is the Load Balancer for the instant messaging
service. It keeps track of the load on each server and
distributes requests dynamically.
|
| |
|
Indication Server |
|
|
This
server maintains user sessions and takes care of IM
functionality except Instant Messaging and Conferencing.
|
| |
|
Messaging Server |
|
|
The Messaging
Server facilitates Instant Messaging and Conferencing.
|
| |
|
Hub Server |
|
|
The Hub
Server maintains status information about all online
users at any point of time and all other servers connect
to this server to use this status information for various
purposes.
|
| |
|
Main Database Server |
|
|
The Main
Database Server based on MY SQL and stores user information.
|
| |
