However, to give the interfaces to modules a consistent structure, we recommend that you follow the conventions as to the form of the supported messages. This facilitates the use of standard code to support the communication, and is in turn facilitated by the existence of such code, for example the supplied Java classes.
I have developed Java classes to support implementing modules. Feel free to use them, or adapt my supplied examples.
Joakim Gustafson has written some Tcl code for implementing and using modules.
The Broker itself is actually a module, which you can call to ask about the modules connected, or be informed when a module disconnects from the broker. This is how the Broker's Graphical User Interface works. See the documentation on the Broker Module.
The Broker communicates using text lines sent over a TCP-connections. The broker interferes as little as possible in the format of what is sent between modules - that is up to the designers of the modules to specify.
© Copyright 1997 Erland
Lewin and the members of the Center
for Speech Technology