Windows service & Web service Interprocess Communication

[Sharon Gorev]

Hello all!

I need an easy way to pass data between windows service & Web service

For example pass a data set, or recordset ,



Both written in C# ,

Both running on the same machine so I'm trying to avoid Sockets / network
communication



Any .Net solution?

Thank you!

Sharon

 

[Sean Hederman]

Using standard remoting in .NET 1.1, you'd have to go through TCP or HTTP.
However Whidbey will have a Named Pipes channel AFIK. Genuine Channels has a
Shared Memory Channel.

 

[Sharon Gorev]

do you recommend c# dotnet named pipes ?
http://www.codeguru.com/Csharp/Csharp/cs_network/remoting/article.php/c7259/

Thank you
Sharon

 

[Sean Hederman]

I think rather use
http://www.gotdotnet.com/Community/...mpleGuid=43a1ef11-c57c-45c7-a67f-ed68978f3d6d.
It's what the page you referenced was based on, and it looks like it'll fit
better into the standard Remoting infrastructure. So if you later decide you
want to switch to TCP or HTTP on remote machines, it should just be a
configuration change.

The code guru example you referenced appears to be geared much more towards
byte sending and receiving (sorta like sockets), whereas the gotdotnet
Channel will allow you to use standard Remoting object semantics.

 

[Sharon Gorev]

Thank you Sean ,
last question , do you recommend any other communication not using
networking ?
Thank you
Sharon

 

[Sean Hederman]

No, if I was you, I'd stick to Remoting across some sort of local channel.
Using the built-in communication scheme should offer you far more
flexibility than rolling your own system.

Named Pipes and Shared Memory should be good enough for in-machine
communication. Hell, TCP's good enough, just not quite as fast.

 

[Sharon Gorev]

like i saidso i think i will go with the Named Pipes and Shared Memory
thank you very much
sharon