Hello,
Could anybody tell me what are IPC mechanisms that .NET supports at
present?(and what improvements were made in different framework versions)?
Is IPC support windows dependent or is it designed to be more or less
portable(does Mono support IPC?)
tia
--
*a*
..Net Remoting was the first. Now, there's Windows Communication Foundation.
http://msdn2.microsoft.com/en-us/webservices/aa740645.aspx
http://msdn2.microsoft.com/en-us/netframework/aa663324.aspx
--
HTH,
Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP
"adrin"
news:fm4ucf$sum$2@news.interia.pl...
> Hello,
> Could anybody tell me what are IPC mechanisms that .NET supports at
> present?(and what improvements were made in different framework versions)?
>
> Is IPC support windows dependent or is it designed to be more or less
> portable(does Mono support IPC?)
>
> tia
>
> --
> *a*
On Thu, 10 Jan 2008 07:01:39 -0500, Kevin Spencer wrote:
> .Net Remoting was the first. Now, there's Windows Communication
> Foundation.
>
> http://msdn2.microsoft.com/en-us/webservices/aa740645.aspx
> http://msdn2.microsoft.com/en-us/netframework/aa663324.aspx
Thanks, so all IPC communication in WCF occurs behind-the-scenes using
named pipes?
--
*a*
named pipes is one option (assuming local); http is another (probably
the most common); or tcp/ip; or msmq... (extensible)
http://msdn2.microsoft.com/en-us/library/ms733769.aspx
Marc
On Thu, 10 Jan 2008 07:01:39 -0500, Kevin Spencer wrote:
> .Net Remoting was the first. Now, there's Windows Communication
> Foundation.
so WCF is intended to replace .NET Remoting in some way?
--
*a*
> so WCF is intended to replace .NET Remoting in some way?
WCF is intended to provide a unified framework for messaging; it can,
indeed, be used as a replacement for remoting or web services - but
one of the key ideas is that the code you write doesn't care about
this... the "how to connect" is usually managed via configuration
files, making it theoretically possible to switch between transports
without changing the code. Of course, LOLA has something to say about
this, but it does a reasonable job of making things more maneagable.
Marc
I have an example that uses named pipes if you want to look at it.
WCF/named pipes.
http://sholliday.spaces.live.com/blog/cns!A68482B9628A842A!1 58.entry
Here is a link I had bookmarked as
well.http://www.danielmoth.com/Blog/2004/09/ipc-with-remotin g-in-net-20.html
"adrin"
news:fm4ucf$sum$2@news.interia.pl...
> Hello,
> Could anybody tell me what are IPC mechanisms that .NET supports at
> present?(and what improvements were made in different framework versions)?
>
> Is IPC support windows dependent or is it designed to be more or less
> portable(does Mono support IPC?)
>
> tia
>
> --
> *a*
Ooops! I hit CNTL S (send) instead of CNTL V
http://www.danielmoth.com/Blog/2004/09/ipc-with-remoting-in- net-20.html
"adrin"
news:fm4ucf$sum$2@news.interia.pl...
> Hello,
> Could anybody tell me what are IPC mechanisms that .NET supports at
> present?(and what improvements were made in different framework versions)?
>
> Is IPC support windows dependent or is it designed to be more or less
> portable(does Mono support IPC?)
>
> tia
>
> --
> *a*