This project is read-only.
Internally the Cubicle Add-In has a Cortex Manager that is responsible for keeping a reference to all Cubicle host connections.

The Cortex Manager has the following responsibilities:
  • Managing connections to multiple Cubicle Hosts
  • Creating and destroying local and AppDomain Cubicle instances.
When a user establishes a connection to an Cubicle Host, that connection is given an alias. This connection alias is used by most of the worksheet functions to designate the target for the operation.

Of the connections in the Cortex Manager, one can be designated as a default. When an alias is omitted from a worksheet function, the default connection will be used as the target.

Three types of client-host connections are possible:

Local Hosts
Local hosts are instances of the Cubicle that are running in the same AppDomain as the Add-In. Interaction with local hosts offer the lowest latency and access to the native Excel API but do not allow users to unload assemblies.

AppDomain Hosts
AppDomain hosts are instances of the Cubicle that run within the Excel Process but within their own AppDomain. Connections to AppDomain hosts have higher latency but can users a means for unloading assemblies without restarting the Excel Process. AppDomain hosts cannot interact with the native Excel API.

Remote Hosts
Remote hosts are instances of the Cubicle that run in a separate process on the local machine or on network servers. These connections have the highest latency but allow users to offload computationally intensive tasks to high capacity servers.

For more information on the functions responsible for connection management, see Cubicle (Management).

Last edited Apr 21, 2013 at 3:48 PM by Tjaart, version 2


No comments yet.