The project tailors the behavior of existing unnamed pipe and provides a different
kind of interprocess communication from the traditional existing IPCs.
The new unnamed persistent pipe ensures
the data written to the pipe is broadcasted to all the related processes. i.e., The data is
preserved in the pipe, until all the readers have read all the available data in the pipe.
Perhaps with a little performance degradation.
The filesystem abstracts the synchronization mechanism from the applications, to make the data persistent
and re-enable the write process.
Development
Currently there are no mailing lists or forums for this project.
The code of the persistent pipe ( un named ) has been checked in. File release is also created and code has been made public.
This code does have some performance degradation impact. The reason being quite simple , the writer is blocked till all
readers have read all the available data from the pipe.
We are working on a way to achieve persistency in an optimized manner and have planned extend the same named pipe.
We would shortly come out with some bench mark between original un named pipe and our implementation.
Sudharsan and Myself were involved in the development process.
Special Thanks to Ramanathan and Ramanan!!!
We would also like to thank Manas Kumar Lenka for his valuable suggestions .
Acknowledgement
We're grateful to Sourceforge.net for hosting this project. We're really impressed
by the Open Source Movement.