



Communications
The Communications directory contains samples that cover the
CommonPoint(TM) Communications framework. Each sample resides in a
separate directory.
MessageStreams is the simplest example of CommonPoint
communications. This sample shows how to create a service definition,
implement a message-streams-based server, access a message-streams-based
server, and make queries to the server.
RPC is a very simple example of the CommonPoint system's RPC
mechanism. It shows how to implement a simple caller-dispatcher pair.
It is intended to be used as an RPC "template": you should be able to
change the class names and put in your own functions fairly easily.
Template RPC is an alternate way of approaching RPC, using
templates. It is a small layer above RPC, to be used as-is, that
allows you to do networking without having to write caller and
dispatcher classes. This functionality is achieved by using a template
caller, a template dispatcher, and by writing functors that act on the
remote data.
Click the icon to mail questions or corrections about this material to Taligent personnel.
Copyright©1995 Taligent,Inc. All rights reserved.