Hi All,
The Name pipe also uses Memory Mapping file under the hood.
Before the appear of the .Net Framework, the windows uses these ways of
inter-proc
communication, so I think the .Net Remoting also uses these classic windows
inter-proc
communication under the hood.
Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| From: "William Stacey" <st*****@mvps.org>
| References: <#E**************@TK2MSFTNGP10.phx.gbl>
<OH**************@TK2MSFTNGP10.phx.gbl> <tSz9b.467147$YN5.318200@sccrnsc01>
| Subject: Re: Is there an alternative to remoting?
| Date: Tue, 16 Sep 2003 10:14:28 -0400
| Lines: 65
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.0
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Message-ID: <ek*************@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: 66.188.59.114.bay.mi.chartermi.net 66.188.59.114
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTN GXA05.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.languages.csharp:184563
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| Not crazy. I have looked for more info on this with little uncovered. I
| seem to remember reading the help pages one time and they talked about
| remoting in the same machine uses optimized communication somehow.
However,
| you still need to ref ports so maybe they just mean they use the local
| loopback instead of going all the way down the network stack. IMO, they
| could use an LPC channel (that maybe uses named pipes under the hood) for
| remoting too. I think a third party makes one. For that matter a shared
| memory arc in the clr would be nice and remove the need for remoting for
| some things. How about being able to publish a shared stream or array (or
| int) and have another app subscribe to that stream using just attributes
on
| fields to denote the intentions.
|
| --
| William Stacey, DNS MVP
|
| "Daniel O'Connell" <on******@comcast.net> wrote in message
| news:tSz9b.467147$YN5.318200@sccrnsc01...
| >
| > "Dmitriy Lapshin [C# / .NET MVP]" <x-****@no-spam-please.hotpop.com>
wrote
| > in message news:OH**************@TK2MSFTNGP10.phx.gbl...
| > > Hello Michael,
| > >
| > > You can perform cross-AppDomain calls as well. The biggest problem
here
| > > would probably be how to get a reference to another application's
| > AppDomain.
| > > This way, as far as I remember, uses the same Remoting mehcanics
| > underneath.
| > >
| >
| > That brings up a question of my own, is there a way in the framework to
| > perform cross app-domain communication without using external methods
| (TCP,
| > pipes, shared memory, etc) or remoting. A low-level inproc communication
| > system that doesn't have the annoyances or restrictions of remoting
| between
| > appdomains could have its uses...
| > Or I could just be crazy, does it matter?
| >
| > > --
| > > Dmitriy Lapshin [C# / .NET MVP]
| > > X-Unity Test Studio
| > >
http://x-unity.miik.com.ua/teststudio.aspx
| > > Bring the power of unit testing to VS .NET IDE
| > >
| > > "Michael Culley" <mi**@nospam.com> wrote in message
| > > news:%2****************@TK2MSFTNGP10.phx.gbl...
| > > > In vb6 it was possible to create an exe as an activeX exe and
| > communicate
| > > > between 2 apps. Now we have remoting which requires opening a tcp
port
| > to
| > > > listen on, which seems kinda crappy cause another app might be using
| the
| > > > same port. Is there an alternative way of communicating between 2
exes
| > on
| > > > the same machine?
| > > >
| > > > Thanks,
| > > > Michael Culley
| > > >
| > > >
| > >
| >
| >
|
|
|
