Messages in this thread |  | | From | "H. Peter Anvin" <> | Subject | Re: bidirectional named pipe? | Date | 8 Feb 2001 15:10:08 -0800 |
| |
Followup to: <3A81D5B4.9CBC9B0D@kasey.umkc.edu> By author: "David L. Nicol" <david@kasey.umkc.edu> In newsgroup: linux.dev.kernel > > How hard would it be to add? The limitation on fifos that you get the same > one every time you open it makes some things tricky -- the server has to > move the fifo and mkfifo a new one to replace its data with something else, > for instance, which is not atomic. > > I don't understand, in the original problem, how the server opens > the named bipipe differently from the servers, to be on one end rather than > the other. > > A way to map a file name to a socket pair would be nice, the first to open > it could get one end of it and everyone else would get the other end, or there > would be a switch. > > You could patch the file system code, I wonder how deep the changes would have > to be, if you did it in terms of lots of fifos. >
I would really like it if open() on a socket would be the same thing to connect to a socket as a client. I don't think it's a good idea to do that for the server side, though, since it would have to know about accept() anyway.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |