From: Nathan Thern <nthern@gmail.com>
To: cygwin@cygwin.com
Subject: Re: General question on the status of named pipes
Date: Mon, 24 Oct 2011 18:47:00 -0000 [thread overview]
Message-ID: <CALEg2urw7-rSCzE=62h=EnctNxZzdryULu33X_-MoNEJvfTU5Q@mail.gmail.com> (raw)
In-Reply-To: <4EA5A683.5000007@redhat.com>
On Mon, Oct 24, 2011 at 12:55 PM, Eric Blake <eblake@redhat.com> wrote:
> Actually, named pipes have _never_ worked, at least according to the full
> set of POSIX rules. It's just that some releases had code that limped along
> better than in other releases for the particular use cases you happened to
> throw at them. cgf is working miracles to get it as far along as he has,
> but it's a very tough job to emulate POSIX fifos on top of windows.
Interesting. I used them successfully for a couple of years with 1.5,
IIRC. My mode of usage was usually something like:
$ mkfifo fifo1 fifo2
$ decode_audio_to_PCM audiofile | tee fifo1 > fifo2 &
$ encode_audio_to_format_1 -o newaudio1 fifo1
$ encode_audio_to_format_2 -o newaudio2 fifo2
This has two distinct advantages over tempfiles for me. I don't have
to wait for the decode to complete before I start to re-encode & I
don't need the disk space for large chunks of uncompressed audio.
NT
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-10-24 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 12:51 Nathan Thern
2011-10-24 17:55 ` Eric Blake
2011-10-24 18:47 ` Nathan Thern [this message]
2011-11-02 3:24 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALEg2urw7-rSCzE=62h=EnctNxZzdryULu33X_-MoNEJvfTU5Q@mail.gmail.com' \
--to=nthern@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).