Reflector - application architecture

Processing distribution

Reflector is build basing on client-server (C/S) technology. It means that part of the program is running on user's computer and another part is running on server host.
User part is usually named 'client part' and as a product is named "Reflector Client".
Server part of the product is named "Reflector Server".
User part can be used by the user to execute some commands on server - from server configuration to status reading commands. It is an unique advantage that thanks to client-server architecture the Reflector user can completely switch off his/her computer or only his/her part of the program and the data processing will continue normally on the server.

Architecture scheme

Below you can find Reflector architecture scheme.

As you can see, Reflector Client is communicating with server using HTTP protocol. On the other side Reflector Server is exchanging messages with e-mail servers using POP3/SMTP protocols.
Reflector Client and Reflector Server can also be running in single-computer configuration (Client and Server running on the same host), however in such a configuration the email message processing will be stopped if you switch off the computer.

Licencing and distribution conditions

The program is distributed as two distinct products: "Reflector Server" and "Reflector Client".

Licence for "Reflector Server" product is required only for one computer - for the server. If we are considering default configuration (one server, many users) there is no need to install and buy "Reflector Server" for more computers.

Licence for "Reflector Client" product is required for each user account who will be using Reflector. This is the reason why this product is much cheaper than "Reflector Server" and it's price is dropping down if you order more licences for this product.