Re: Interprocess communication.

Tech-Archive recommends: Speed Up your PC by fixing your registry



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@xxxxxxx> wrote in message
news:486a6ce9$0$25788$9b622d9e@xxxxxxxxxxxxxxxxxx
Mufasa wrote:

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-oriented_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


.



Relevant Pages

  • Re: what type of socket should I use?
    ... Essentially the server just waits till it gets a message ... | from the client and on reciept of a message it send ... sockets, Named Pipes, or Shared Memory ... Unix Domain Sockets is similar to Named Pipes. ...
    (comp.os.linux.networking)
  • Re: what type of socket should I use?
    ... Essentially the server just waits till it gets a message ... | from the client and on reciept of a message it send ... sockets, Named Pipes, or Shared Memory ... Unix Domain Sockets is similar to Named Pipes. ...
    (comp.os.linux.development.apps)
  • Re: Delegation???
    ... EFS in Win2k relies on delegation working over named pipes, ... client and server, where the server can connect to another server as well. ...
    (microsoft.public.platformsdk.security)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Re: Client Server Architektur um Verzeichnisse mit Teilweise großen Datein auszutauschen
    ... MSMQ oder einen der Open Source Message Broker wie Apache ActiveMQ (für ... den es auch einen .Net Client gibt). ... Der Message Broker ist dann ein zentraler Speicher, ... Und .Net Remoting mit SOAP. ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)