named-pipes

I am trying to use named pipes to communicate between a server and a client process on the same machine. server sends a message to client, client does something with it and returns a result, and server is supposed to get the result. here is the code for server: using System; using System.IO; using System.IO.Pipes; class PipeServer { static void Main() { using (NamedPipeServerStream pipeServer = new NamedPipeServerStream("testpipe", PipeDirection.InOut)) { Console.WriteLine("NamedPipeServerStream object created."); // Wait for a client to connect Console.Write("Waiting for client connection..."

When using C# NamedPipeServerStream, in case a client doesn't send any message-end-pattern (like \r\n when server reads with ReadLine()) NamedPipeServerStream Read methods will wait forever and no Abort() or Interupt() methods will work on that thread. Since: 1) Stream.ReadTimeout not supported for NamedPipeServerStream 2) Abort() or Interupt() doesn't work on thread 3) NamedPipeServerStream.Disconnect() nether work It is unclear, how to setup timeout on NamedPipeServerStream read operations? Let me introduce an example. The specification of IPC we have require an exchange of \0-terminated

Is there any way for a writer to know that a reader has closed its end of a named pipe (or exited), without writing to it? I need to know this because the initial data I write to the pipe is different; the reader is expecting an initial header before the rest of the data comes. Currently, I detect this when my write() fails with EPIPE . I then set a flag that says "next time, send the header". However, it is possible for the reader to close and re-open the pipe before I've written anything. In this case, I never realize what he's done, and don't send the header he is expecting. Is there any

I created a fifo file using mkfifo . Is it possible to open/write to this without blocking? I'd like to be agnostic whether there is a reader or not. The following: with open('fifo', 'wb', 0) as file: file.write(b'howdy') Just stalls at the open until I do a cat fifo from another shell. I want my program to make progress regardless there's a data consumer watching or not. Is there a different linux mechanism I should be using perhaps? From man 7 fifo : A process can open a FIFO in nonblocking mode. In this case, opening or read-only will succeed even if no-one has opened on the write side yet,

Currently I am working on a multi-process desktop application on Windows. This application will be a shrink wrapped application which will be deployed on client machines across the world. While we can have broad specifications for the machines - e.g. Windows XP SP3 with .Net 4.0 CF, we wont have control over them and we cant be too specific on their configuration - e.g. we cannot specify the machine must have a cuda 1.4 capable graphic processor etc. Some of these processes are managed (.Net 4.0) and others are unmanaged (C++ Win32). The processes need to share data. The options I have

I have a python script that uses multiprocessing.pool.map to do some work. As it goes it prints things to stdout , for errors it prints to stderr . I decided it would be nice to have a separate log file for each of the streams and after a bit of thinking worked out that I should run it like this: time ./ecisSearch.py 58Ni.conf 4 1 > >(tee stdout.log) 2> >(tee stderr.log >&2) This gives me the log files and preserves the output on the appropriate streams. However here comes the problem. If I run it without the redirects I get this: $ time ./ecisSearch.py 58Ni.conf 4 1 2015-01-09 14:42:37.524333