With Carapace, communication is done via a stack of modules as in the following diagram:
Stackable modules give you very flexible communications -- for example, if you want to do the TELNET protocol over TCP/IP, then the two modules are as follows:
If, at some later date, that service now insists on even-parity communications, you can re-configure the stack to include a in a Util module to do the required parity conversion:
Stackable modules avoid duplication of functionality. In the above examples, our TCP/IP module needs know nothing about parity or telnet. In the same way, we could put on a different bottom module (eg. to do IPX/SPX communications) and that, too, would not need to know about parity etc.
| build | building a comms stack to a service |
| modules | standard methods offered by a comms module |
| built-in modules | modules and communications-related classes which are built-in to Carapace |
| scripted modules | defining your own comms modules |
| configuration | configuration of a comms stack |
| logging | recording the data transferred |
| Contents | Index | Current topic: communications | Related topics: communications classes, objects |