Home

Castle Stronghold

Table of contents

  • 1 Configuration
  • 2 Supported Scenarios

Using it

The facility works on both server and client side, and you can even have a situation where the application serves as both endpoints.

The remoting configuration (channels, formatters) is external and it is the same file that is accepted by .net remoting. Please check its official documentation.

For each component that is remote (client or server) you must supply the remoting strategy. We currently support:

Configuration

The following depicts the full configuration scheme for the facility. Most of the attributes are optional or only required for some specific scenarios. The scenarios will be discussed further in this document.


<facility 
  id="remote.facility" 
  isServer="true|false"
  isClient="true|false"
  kernelUri="a valid identifier"
  remoteKernelUri="a full uri including protocol, host, path and resource"
  remotingConfigurationFile="absolute or relative path to the remoting configuration file" />

The following depicts the attributes which are available on the component nodes:


<component 
  id="" 
  remoteclient="singleton|singlecall|clientactivated|component|recoverableComponent " 
  uri="required for singleton, singlecall and recoverableComponent but if not present, the component id is used" />

Supported Scenarios

There are varios situations where the Remoting Facility can become handy. The following sections exemplifies each one and presents any caveat that they might have.

Google
Search WWW Search castleproject.org