Re: Communications Between Program and Controlling Program
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Wed, 31 May 2006 17:03:59 -0400
Named pipes if you are working within a single Windows domain (or domains with mutual
trust arrangements) and want security.
Sockets if you need to work across multiple domains. At that point, concepts like SSL and
other encryption layers have to be dealt with or any 12-year-old (of any age) with a
network connection can attack you.
Mailslots are not "reliable" communications mechanisms.
Also, no matter what your protocol is, make sure that you can handle multiple startup
messages, multiple shutdown messages, etc. (I built such a pair of programs, and debugging
them was a nightmare until I built a robust protocol so that either could be shut down and
restarted and the protocol would resynchronize)
joe
On 30 May 2006 13:55:35 -0700, "Jeff" <noloader@xxxxxxxxx> wrote:
Hi All,Joseph M. Newcomer [MVP]
I should have speciifed the kind of feedback:
Named Pipes \ Mailslot versus a socket, etc.
Jeff
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- References:
- Prev by Date: how to copy/paste international strings to the VS editor?
- Previous by thread: Re: Communications Between Program and Controlling Program
- Next by thread: Modeless dialog closing a modal dialog problem
- Index(es):
Relevant Pages
|