Scenario: Using the container on both endpoints but just to configure remoting

» Home » MicroKernel/Windsor » Documentation » Facilities » Remoting Facility » Scenario: Using the container on both endpoints but just to configure remoting

KernelOnBothEndPoints.Sample.zip (10.4k)

You may also use the container and the facility on both endpoints but just to configure .net remoting.

The following snippets exemplifies this usage.

Client Container Configuration
Server Container Configuration


<castle>

    <facilities>
        <facility 
            id="remote.facility" 
            type="Castle.Facilities.Remoting.RemotingFacility, Castle.MicroKernel"
            baseUri="tcp://localhost:2133"
            remotingConfigurationFile="RemotingTcpConfigClient.config">
        </facility>    
    </facilities>
    
    <components>
        <component 
            id="remoteconsolecomponent" 
            service="Example.Shared.IRemoteConsole, Example.Shared"
            type="System.Object, mscorlib"
            remoteclient="singleton" />
    </components>

</castle>


<castle>

    <facilities>
        <facility 
            id="remote.facility" 
            type="Castle.Facilities.Remoting.RemotingFacility, Castle.MicroKernel"
            remotingConfigurationFile="RemotingTcpConfig.config">
        </facility>    
    </facilities>
    
    <components>
        <component 
            id="remote.console.component" 
            service="Example.Shared.IRemoteConsole, Example.Shared"
            type="ServerApp.RemoteConsoleImpl, ServerApp"
            remoteserver="singleton" uri="remoteconsolecomponent" />
    </components>

</castle>

Home

Castle Stronghold

Scenario: Using the container on both endpoints but just to configure remoting