Re: Interprocess communication.

Mufasa wrote:

Quote:

You talk about webservices and I've used them extensively but I don't see
how they could work here for most of the stuff. Aren't web services passive?
They can't instigate some kind of action. I would need to do things like
every 15 minutes check with our home server to see if there are any changes
it needs to be aware. And also every 5 minutes tell the 'software watchdog'
that it's still alive.

Message Oriented Middleware might be an option too:

http://en.wikipedia.org/wiki/Message...ted_middleware

There are many very good (including Open Source implementations) and
most of them support .NET, so you can have active and passive components
on the client. The message broker can notify the client about new
information, and the client can send its status back to the server any time.

I wrote Delphi client libraries for some message brokers. MOM solutions
are easy to implement and very useful in medium and large scale systems.
They are not well known in the developer community yet but with service
oriented architecture they will be more common soon.

Hope this helps(tm)
--
Michael Justin
SCJP, SCJA
betasoft - Software for Delphi™ and for the Java™ platform
http://www.mikejustin.com - http://www.betabeans.de

It looks like I'm going to do named pipes. Can anybody point me to code
samples (or a class ) that does the pipes for me?

The examples I've seen are .Net 2.0 and are making WinAPI calls.

I'll be using .Net 2.0.

TIA - Jeff.

"Michael Justin" <michael.justin@gmx.netwrote in message
news:486a6ce9$0$25788$9b622d9e@news.freenet.de...

Quote:

Mufasa wrote:
>

Quote:

>You talk about webservices and I've used them extensively but I don't see
>how they could work here for most of the stuff. Aren't web services
>passive? They can't instigate some kind of action. I would need to do
>things like every 15 minutes check with our home server to see if there
>are any changes it needs to be aware. And also every 5 minutes tell the
>'software watchdog' that it's still alive.

>
Message Oriented Middleware might be an option too:
>
http://en.wikipedia.org/wiki/Message...ted_middleware
>
There are many very good (including Open Source implementations) and most
of them support .NET, so you can have active and passive components on the
client. The message broker can notify the client about new information,
and the client can send its status back to the server any time.
>
I wrote Delphi client libraries for some message brokers. MOM solutions
are easy to implement and very useful in medium and large scale systems.
They are not well known in the developer community yet but with service
oriented architecture they will be more common soon.
>
Hope this helps(tm)
--
Michael Justin
SCJP, SCJA
betasoft - Software for DelphiT and for the JavaT platform
http://www.mikejustin.com - http://www.betabeans.de

Hi, I also have the same problem.
Have you finalize your work in Named Pipes?
i came across with this two..it may help..
http://msdn.microsoft.com/en-us/library/bb546102.aspx

http://www.eggheadcafe.com/articles/20060404.asp

For me my problem is to know which IPC will be the fastest?
(Pipes, .Net Remoting, WM_COPYDATA, Sockets)
What made you decide to use Pipes?

TIA - Dan

Dan,

It's impossible to say which one is fastest, unless you give the details
of the messaging pattern, the payload, etc, etc.

Also, you might not have the need for something that is the fastest,
depending on what your goals are. You might find that using named pipes in
WCF is fast enough, while making development easier, which is better than
something that you have to maintain yourself.

In the end, the trade off is something that you will have to decide on.

--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

<Danwrote in message news:20081132397dantericafort@gmail.com...

Quote:

Hi, I also have the same problem.
Have you finalize your work in Named Pipes?
i came across with this two..it may help..
http://msdn.microsoft.com/en-us/library/bb546102.aspx
>
http://www.eggheadcafe.com/articles/20060404.asp
>
For me my problem is to know which IPC will be the fastest?
(Pipes, .Net Remoting, WM_COPYDATA, Sockets)
What made you decide to use Pipes?
>
TIA - Dan
>
>

Re: Interprocess communication.

re: Re: Interprocess communication.

re: Re: Interprocess communication.

re: Re: Interprocess communication.

Similar C# / C Sharp bytes

/bytes/development

/bytes/it

/bytes/about