Re: Interprocess communication
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Tue, 18 Apr 2006 10:32:40 -0400
Multicast has some problems, such as how any routers in the local network handle it.
Depending on the configuration issues, it can be that the router will block the multicast
(and routers typically block broadcasts as well). The client/server idea is the best
suggestion.
joe
On Mon, 17 Apr 2006 12:45:37 -0700, "Michael K. O'Neill"
<MikeAThon2000@xxxxxxxxxxxxxxxxxx> wrote:
"Ajay Kalra" <ajaykalra@xxxxxxxxx> wrote in messageJoseph M. Newcomer [MVP]
news:1145279893.038169.9570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This will require a client server type application. All the clients
should send a message at start up. Server should essentially be running
at all times. When server receives the startup message, it can
communicate with the clients and initialize these if wante. Typically
you will also have a heartbeat that is sent fromt he client to the
server. This tells the server that the client is alive/active.
---
Ajay
Wouldn't IP multicast eliminate the need for this kind of server?
Mike
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
--
NewsGuy.Com 30Gb $9.95 Carry Forward and On Demand Bandwidth
.
- References:
- Interprocess communication
- From: Serj Kondryukov
- Re: Interprocess communication
- From: Ajay Kalra
- Re: Interprocess communication
- From: Michael K. O'Neill
- Interprocess communication
- Prev by Date: Access to HTML objects inside a particular frame on a multi-framed web pages throught Microsoft HTML interface DLL programtically
- Next by Date: Re: Programmatically detecting personal firewalls blocking my app
- Previous by thread: Re: Interprocess communication
- Next by thread: Re: Interprocess communication
- Index(es):
Relevant Pages
|