ComNet is also an open communications server.

This means that any Application can use ComNet as its communications handler, simply by opening ComNet and then using only basic Guardian calls such as write and read. This now provides the Application with connectivity to any of the protocols supported by ComNet. Furthermore, the Application inherits the other benefits of ComNet such as automatic backup connection capabilities.

Clearly, this simplifies and expedites Application development since the expertise and complexities of specific protocol handling development, testing and maintenance have been removed.

Another benefit is that this gives you a fast, simple and standard approach to implementing and maintaining your communications handling requirements; simply use write and read.

For example, the first diagram below shows an Application which has had its own TCP/IP communications handler developed in-house. This would have required a significant level of protocol-specific expertise and effort from the developer to cater for partial transmissions, retransmissions, assembling raw message data into logical application messages and other such considerations. It may not have even included any backup connection capability.

The next diagram shows how ComNet has been used to provide the TCP/IP protocol handling on behalf of the Application. The Application simply opens ComNet and then uses standard Guardian write and read calls. ComNet takes care of the rest, including backup connection management if required.

If, for whatever reason, your Application ever requires the use of a different protocol then it's simply a matter of modifying the ComNet session's configuration. This can even be done online without disturbing any other active ComNet sessions.