The InterCom system not only solves the above problem, but also enables developers to incorporate new functionality and build new types of applications that were previously regarded as too difficult or too arduous. The InterCom system consists of the InterCom server and InterCom clients. The server is installed on a machine that can be reached by the clients that require its services. The server keeps track of location and status of all clients connected to it, therefore the clients never need to know the location of other clients within the network. Clients are implemented as controls that are incorporated within your application.
Notification is based on a publisher-subscriber metaphor.
The main concept within InterCom notification is that of 'events'. An event, not to be confused with control events such as 'click', is a named incident, i.e. a name you define for an incident that can occur within time. For example, changes made to a particular table in a database is an incident which we could call 'Table1Changed'. Events need not be discrete incidents however, they can also be continuous incidents, such as 'DataReady'. An event is whatever you name it.