Client/server communication using named pipe

[Tumurbaatar S.]

Hi!
I'm going to use the named pipe in my system. The system consists of one
server
and 2-3 clients. The server commonly receives messages sent by clients. I.e.
communication
is one-way, from clients to the server. Though some acknowledgement (OK/ACK)
can be
sent from the server after receiving a message from a client.
My question is about whether to keep connections or not. The system should
work
up to 10 hours without a break. The clients do not send messages too often.
Only 1..2 command per 1 minute. Also, if some failure occurs on the server
(or on LAN)
then the server application may be restarted. Same for client programs.
So, what is the preferred way: use CreateFile() or CallNamedPipe() at client
program?

[Arkady Frenkel]

From security point of view the less open connections in the system the
better
Arkady

Post by Tumurbaatar S.
Hi!
I'm going to use the named pipe in my system. The system consists of one
server
and 2-3 clients. The server commonly receives messages sent by clients.
I.e. communication
is one-way, from clients to the server. Though some acknowledgement
(OK/ACK) can be
sent from the server after receiving a message from a client.
My question is about whether to keep connections or not. The system should
work
up to 10 hours without a break. The clients do not send messages too often.
Only 1..2 command per 1 minute. Also, if some failure occurs on the server
(or on LAN)
then the server application may be restarted. Same for client programs.
So, what is the preferred way: use CreateFile() or CallNamedPipe() at
client program?