Chaining WXF services

I would appreciate some architectural advice on chaining services.

As an example I have two discrete services hosted in a single Windows
service.
For most of the time these services are accessed by clients to provide non
related functionality but in one case service A needs to call service B in
order to fulfil a client request.

The obvious solution would be for service A to act as a standard client of
service B (Service Reference from Visual Studio etc) but this seems
inefficient as both services are hosted in the same process and establishing
a communications channel to effectively talk to yourself seems unnecessary.

Is there any way of services hosted in the same process chaining calls
without this overhead ?

Instance the class directly with new and call the service method.

"Graham Wright" <grahamwright@msn.com> wrote in message
news:uZ%23dK%23ERHHA.4276@TK2MSFTNGP02.phx.gbl...
>I would appreciate some architectural advice on chaining services.
>
> As an example I have two discrete services hosted in a single Windows
> service.
> For most of the time these services are accessed by clients to provide non
> related functionality but in one case service A needs to call service B in
> order to fulfil a client request.
>
> The obvious solution would be for service A to act as a standard client of
> service B (Service Reference from Visual Studio etc) but this seems
> inefficient as both services are hosted in the same process and
> establishing a communications channel to effectively talk to yourself
> seems unnecessary.
>
> Is there any way of services hosted in the same process chaining calls
> without this overhead ?
>

look for generic approach in "Sharing an Instance"
http://msdn.microsoft.com/msdnmag/is...WCFEssentials/.

Arkady

"Graham Wright" <grahamwright@msn.com> wrote in message
news:uZ%23dK%23ERHHA.4276@TK2MSFTNGP02.phx.gbl...
>I would appreciate some architectural advice on chaining services.
>
> As an example I have two discrete services hosted in a single Windows
> service.
> For most of the time these services are accessed by clients to provide non
> related functionality but in one case service A needs to call service B in
> order to fulfil a client request.
>
> The obvious solution would be for service A to act as a standard client of
> service B (Service Reference from Visual Studio etc) but this seems
> inefficient as both services are hosted in the same process and
> establishing a communications channel to effectively talk to yourself
> seems unnecessary.
>
> Is there any way of services hosted in the same process chaining calls
> without this overhead ?
>

In addition you can use
http://groups.google.com/group/micro...291b7474a06cac
Arkady

"Arkady Frenkel" <arkadyf@hotmailxdotx.com> wrote in message
news:eRjH%23ReRHHA.1200@TK2MSFTNGP04.phx.gbl...
> look for generic approach in "Sharing an Instance"
> http://msdn.microsoft.com/msdnmag/is...WCFEssentials/.
>
> Arkady
>
> "Graham Wright" <grahamwright@msn.com> wrote in message
> news:uZ%23dK%23ERHHA.4276@TK2MSFTNGP02.phx.gbl...
>>I would appreciate some architectural advice on chaining services.
>>
>> As an example I have two discrete services hosted in a single Windows
>> service.
>> For most of the time these services are accessed by clients to provide
>> non related functionality but in one case service A needs to call service
>> B in order to fulfil a client request.
>>
>> The obvious solution would be for service A to act as a standard client
>> of service B (Service Reference from Visual Studio etc) but this seems
>> inefficient as both services are hosted in the same process and
>> establishing a communications channel to effectively talk to yourself
>> seems unnecessary.
>>
>> Is there any way of services hosted in the same process chaining calls
>> without this overhead ?
>>
>
>