Comms Service Configuration

The configuration for a Service contains all information required to connect to that service ie.

the named stack or the list of comms modules required to form the communications channel
all the relevant properties which configure the modules on the comms stack

This is used in conjunction with the module configuration which defines how to load and create each comms module.

Apart from the following two attributes, all other attributes must be valid properties for the identified stack:

`modules`	comma-separated list of names of comms modules -- each module must match the name of a sub-section of HKEY_CURRENT_USER:Software/Carapace/Communications/Modules
`stack`	name of a comms stack -- the stack name must match the name of a sub-section of HKEY_CURRENT_USER:Software/Carapace/Communications/Stacks

Every Service section must have either a modules attribute or a stack attribute.

For example, suppose we wanted to connect to a Unix box using Telnet. We could then set up a Service section called Unix which contains the following attributes:

    host="myserver.myco.co.uk"
    port=23
    modules="Telnet,Tcp"

Contents

Index

Current topic: communications

Related topics: communications classes, objects