Configuring the Dispatcher

You need to configure the dispatcher in order to collaborate with others on a project. For configuration information, please select from the following sections from our step-by-step tutorial:

Working with the Dispatcher

Dispatcher icon

Other than during the initial setup, the Dispatcher tries to be as unobtrusive as possible. You will only see its icon on your taskbar. When this icon turns red and sprouts arrows, it means that there are some scripts waiting to be dealt with.


To open the dispatcher, click on the Dispatcher icon and select "View Diagnostics". A window will pop up with five tabs as shown below.

Quarantine tab

Quarantine Tab

The quarantine tab will alert you to any problems with routing scripts locally. For example, if you receive an invitation to join a project, the scripts associated with this invitation will remain in quarantine until you provide a root path for the project files. To release a script from quarantine, select the script and click the up arrows.

Alert Log

Alert Log tab

The alert log notifies you and records any problem dispatching scripts whether over LAN or Email.

Public Inbox tab

Dispatcher's list of mailboxes

The Public Inbox will list any scripts waiting to be routed. Double-clicking on a script will show you the details for that script (such as project, sender, recipients, etc.). Typically, this will be empty unless your are offline.

Members Tab

Dispatcher's list of project members

The Member's tab lists all local project members. On a Hub, it also lists satellite members. The display is organized by the project. You can double-click on each entry to see the list of (local and satellite) members for that project. This is the place where you can edit satellite members' local transport. This is usually a network path of the form \\SATELLITE\CODECOOP. If your machine is a satellite, this list should not contain any satellite members--the location column may only contain here.

Remote Hubs

List of remote hubs

The last tab contains a list of known remote Hubs and their email addresses.

Outgoing scripts are automatically dispatched by default, unless you're on a Hub with emailing set to manual. In that case, select Send email from the All menu, or from the Dispatcher's context menu, which pops up when you right-click on its icon. The context menu also contains the Get email command that lets you retrieve scripts directly from your email program (rather than waiting for automatic retrieval). Scripts also tend to accumulate in the Public Inbox when some network connections are down.