From: Norton Allen <allen@huarp.harvard.edu>
To: Ken Brown <kbrown@cornell.edu>, cygwin <cygwin@cygwin.com>
Subject: Re: Sv: Named pipes and multiple writers
Date: Thu, 26 Mar 2020 13:00:20 -0400 [thread overview]
Message-ID: <c1b769da-1ffe-e991-ebf7-fc55fd42afb0@huarp.harvard.edu> (raw)
In-Reply-To: <5a308064-405a-a231-dee4-56d10d7cd7c9@cornell.edu>
On 3/26/2020 12:44 PM, Ken Brown via Cygwin wrote:
> On 3/26/2020 12:03 PM, Norton Allen wrote:
>> On 3/26/2020 11:11 AM, Ken Brown via Cygwin wrote:
>>>
>>> BTW, I've been working on adding support for multiple readers. I
>>> expect to have a first cut ready within a week or two. Would you
>>> have any use for that? If so, I could revive the topic/fifo branch
>>> and push my patches there for you to test.
>>>
>>
>> Ken, what are the semantics for multiple readers? Do all readers see
>> the same data, or is it first come first served or something else?
>
> It's first come, first served. If two readers attempt to read
> simultaneously, it's possible that one will get some of the available
> input and the other will get some more.
>
> The only use case for multiple readers that I've come across of is
> Midnight Commander running under tcsh. I didn't dig into the code
> enough to know why they do it, or why only under tcsh. See
>
> https://sourceware.org/pipermail/cygwin/2019-December/243317.html
>
> and
>
> https://cygwin.com/pipermail/cygwin-apps/2019-December/039777.html
>
> That's what got me interested in this. It would be nice to know if
> there are other use cases.
>
I suppose it could be used as a simple approach to deploying jobs to
worker processes, provided a process could guarantee that it received
enough information to define a job and not more than one. I guess if the
job definition were fixed length that could work.
next prev parent reply other threads:[~2020-03-26 17:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 11:11 sten.kristian.ivarsson
2020-03-25 12:44 ` Ken Brown
[not found] ` <18be01d602ab$0bbfca30$233f5e90$@gmail.com>
2020-03-26 14:06 ` Sv: " Ken Brown
2020-03-26 15:11 ` Ken Brown
2020-03-26 16:03 ` Norton Allen
2020-03-26 16:44 ` Ken Brown
2020-03-26 17:00 ` Norton Allen [this message]
2020-03-26 22:01 ` Sv: " sten.kristian.ivarsson
2020-03-26 22:39 ` Ken Brown
2020-03-26 23:19 ` Ken Brown
2020-03-27 13:10 ` Ken Brown
2020-03-27 14:53 ` Sv: " sten.kristian.ivarsson
2020-03-27 22:56 ` Ken Brown
2020-03-27 23:00 ` Ken Brown
2020-03-28 12:10 ` Sv: " sten.kristian.ivarsson
2020-03-28 15:43 ` Ken Brown
2020-03-29 2:19 ` Ken Brown
2020-03-30 17:44 ` Ken Brown
2020-03-31 21:10 ` Sv: " sten.kristian.ivarsson
2020-03-31 22:02 ` Ken Brown
2020-04-01 7:45 ` Sv: " sten.kristian.ivarsson
2020-04-01 13:47 ` Ken Brown
2020-04-01 8:52 ` sten.kristian.ivarsson
2020-04-01 16:15 ` Ken Brown
2020-04-01 17:14 ` Sv: " sten.kristian.ivarsson
2020-04-01 18:34 ` Ken Brown
2020-04-02 2:19 ` Ken Brown
2020-04-02 8:05 ` Sv: " sten.kristian.ivarsson
2020-04-02 12:47 ` Sv: Sv: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple wri Gregery Barton
2020-04-02 18:21 ` Sv: Sv: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple writers Ken Brown
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=c1b769da-1ffe-e991-ebf7-fc55fd42afb0@huarp.harvard.edu \
--to=allen@huarp.harvard.edu \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).