In version 4, large companies could install several Pigeon Servers and connect them to a Pigeon Gateway in order to synchronize them and enable the distribution of messages at each server. In ePigeon Instant Messaging 5, this configuration has been replaced by an ePigeon Agents network and a single ePigeon Server. The ePigeon Agents serve as “multiplexers”, accepting several ePigeon Client connections and only requiring a single connection to an ePigeon Server. This configuration offers the advantage of reducing the workload imposed on the ePigeon Server and of increasing the speed of sending messages to all the ePigeon Clients.
A company with several thousand clients will benefit from this advantage by installing as many ePigeon Agents as necessary to meet their objectives.
Simple network |
Extended network |
|
|
New requirements
In order for it to run, the ePigeon Server and the ePigeon Agent require “Microsoft .NET Framework 1.1” to be installed on the machine. This requirement is not applicable for ePigeon Clients.
New databases
The ePigeon Server now uses VistaDB database engine. All active messages and packages are recorded in the database along with the ePigeon groups, the shared templates and the individual policies of certain users.
ePigeon Clients also use a VistaDB database engine, one local database for each machine user. They save the messages generated by the user, the personal groups, the personal templates and the messages received. Contrary to previous versions, a scheduler is now part of the ePigeon Client, thereby reducing the workload of the ePigeon Server and also reducing the bandwidth of your network. With this new configuration, even if communications break down between the Client and the Server, the scheduled messages will be displayed.