Re: [PATCH 2 of 4 RFC] chgcache: implement simple IPC mechanism

2017-02-15 Thread Yuya Nishihara
On Tue, 14 Feb 2017 11:05:00 -0800, Jun Wu wrote: > Excerpts from Yuya Nishihara's message of 2017-02-14 22:49:34 +0900: > > On Mon, 13 Feb 2017 09:46:21 -0800, Jun Wu wrote: > > > Excerpts from Yuya Nishihara's message of 2017-02-13 23:00:25 +0900: > > > > Why not os.pipe()? > > > > > > > > We

Re: [PATCH 2 of 4 RFC] chgcache: implement simple IPC mechanism

2017-02-14 Thread Jun Wu
Excerpts from Yuya Nishihara's message of 2017-02-14 22:49:34 +0900: > On Mon, 13 Feb 2017 09:46:21 -0800, Jun Wu wrote: > > Excerpts from Yuya Nishihara's message of 2017-02-13 23:00:25 +0900: > > > Why not os.pipe()? > > > > > > We share the same (dup-ed) file descriptors. In this case, the

Re: [PATCH 2 of 4 RFC] chgcache: implement simple IPC mechanism

2017-02-14 Thread Yuya Nishihara
On Mon, 13 Feb 2017 09:46:21 -0800, Jun Wu wrote: > Excerpts from Yuya Nishihara's message of 2017-02-13 23:00:25 +0900: > > Why not os.pipe()? > > > > We share the same (dup-ed) file descriptors. In this case, the write end can > > be used by many forked processes, but IIRC the read end can't.

Re: [PATCH 2 of 4 RFC] chgcache: implement simple IPC mechanism

2017-02-13 Thread Jun Wu
Excerpts from Yuya Nishihara's message of 2017-02-13 23:00:25 +0900: > Why not os.pipe()? > > We share the same (dup-ed) file descriptors. In this case, the write end can > be used by many forked processes, but IIRC the read end can't. Only one > reader can read out a message. So I think there's

[PATCH 2 of 4 RFC] chgcache: implement simple IPC mechanism

2017-02-08 Thread Jun Wu
# HG changeset patch # User Jun Wu # Date 1486601798 28800 # Wed Feb 08 16:56:38 2017 -0800 # Node ID 8410c4a6703bed4b459cf8d62bd32fdcb1e7 # Parent 138f7ba58a70de9610713b8bd55d1ba0ac468fa6 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull