... channel.^1.1

However, other clients may create a new channel with the same name.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... them.^1.2

Note that the Ensemble executable (outboard) has to be available. Also, there has to be a gossip process started if IP multicasting is not available. Refer to [Hay98] for details.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... service.^2.1

This service has not yet been implemented.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... toolkits.^2.2

Note that those patterns that require a channel most often only require a SEND and RECEIVE Java interface. Patterns that are not directly layered on top of channels are named utility patterns.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... messages.^2.3

This would be different in a push-style channel, where all clients are notified when messages arrive.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... thread^2.4

More than a single thread can be created when heavy load is expected.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... request.^2.5

Whether a message is a request or a response is determined in by a flag in the message itself.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.