Yes. The LPC channel was created to address this without going over the
network. But that comes in 2.0. You can still use standard remoting today
and just use the loopback address. Then when 2.0 comes out, you can just
change the URI and everything else should stay the same. One reason why
this may be good for you.
--
William Stacey, MVP
http://mvp.support.microsoft.com
"Susan" <Su***@discussions.microsoft.com> wrote in message
news:2D**********************************@microsof t.com...
Both applications are on the same machine and do not need to connect to
the intranet at all. The only reason that there are two applications instead
of being ocmbined into one is because there is no thread safety in the one
application and this was easier to fix with the one application being
separated into two with the "new" app started as a new process and getting
the info it needed through a private message queue. Is remotting still
applicable?
Thanks,
Susan
"William Stacey [MVP]" wrote:
Remoting will have LPC channel (using NamedPipes) in 2.0. So you could
develope using Remoting today and switch to "LPC://" when that comes
out.
--
William Stacey, MVP
http://mvp.support.microsoft.com
"Susan" <Su***@discussions.microsoft.com> wrote in message
news:02**********************************@microsof t.com... Can someone please point me to a web site or other documentation on
how to use named pipes or an example would be nice? We are currently using a
private message queue are are trying to switch to namedpipes because of some
issues. Any help would be appreciated. :)
Thank you,
Susan
