Configuration Using the Config String

Configuration of the XcoAppSpace is possible in two different ways: Either with a config string, or by using a fluent interface. This page describes configuration with the config string.


Using the config string is very simple: You just hand your config string over to the XcoAppSpace using the appropriate constructor (you have probably already seen this in the previous examples):
var space = new XcoAppSpace(configString);
The config string is structured as a list of name-value pairs, like this:
The name can be any name that is supported by the appspace, for example tcp.port. As you can see by this example, a configuration name is normally structured by a dot, where the first part of the name describes the service which should be configured (in this case tcp), and the second part describes the property of the service (in this case port).

By default, a rule for configuration is: Only services that are configured in the config string are active within the appspace instance. This means that e.g. if the config string contains "tcp.port", an instance of the tcp transport service is added to the space. If there is no configuration name of the tcp transport service contained in the config string, the space instance will not have a tcp transport service. Or, another example: If the config string contains "security.policy", an instance of the basic security service will be added, otherwise no security service will be used.
You can find an overview of the service and properties that can be configured below.


The following code shows the instantiation of the XcoAppSpace with an example configuration using multiple config values:
var space = new XcoAppSpace(
    "tcp.port=8000;;tcp.isdefault=true;" + 
    ";jabber.password=xco001;;" + 
In this case, the XcoAppSpace is instantiated with both a tcp and a jabber transport service. The tcp transport service is configured to be the default (meaning it is by default used for connecting to remote workers) and named "tcp". The jabber service is configured a jid, username and password, and the name "jabber" (this is the name that has to be used when wanting to connect to a worker of the jabber transport service). Additionally, the CCR thread count is configured to the fixed number of 8 threads (if not explicitly configured, the thread count would be equal to the number of CPUs in your PC, or 2 if you only have a single CPU).

Configuration Properties Overview

The following services can be configured:

Last edited Dec 21, 2012 at 1:00 PM by thomass, version 8


No comments yet.