What are the differences between pipes in Windows and Linux?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
No related questions found
One difference that I know of, is that named pipes under Linux are actual entries in the filesystem (you’ll see it in a directory listing, they have a special type), whereas on Windows they are stored in some magical repository somewhere (they are all accessed via the path ‘\\.\pipe\’.
Secondly, in Linux you can just write/read from pipes as if they were any other file, using standard file IO methods. Whereas on windows, you have to use the special ‘Pipe’ functions which are part of the Win32 API.
I like linux’s method better, because it lets me use pipes with any app I want. Eg:
This lets me pipe the output of the MP3 decoder directly into the video decoder, instead of having to first decode the entire MP3 into a WAV file on disk. It’s handy if you have a dual-core CPU, because then you are running both operations at once, for a nice speedup.