Tiago Lam
9526ffa80f
Similarly to how the "tcp:" in Redox's netstack supports opening a first empty scheme, only to later on being dup()'ed and set with an appropriate path, this follows the same approach - a map of NullFile structs is kept and initially associated with an id. Next time dup() is called, the true Handle is created, keeping the same definitions of the previously created NullFile. Not that it is important to add support for this in the ipcd to support AF_UNIX sockets, otherwise the socket() created in relibc won't be associated with a address / path.
ipcd
A userspace daemon for interprocess communication.
Usage
See the examples folder.
Simply open chan:<name> with O_CREAT where <name> is any name you'd like to create a listener.
This listener can accept clients by calling dup("listen").
Open chan:<name> without O_CREAT to connect. Now you can read and write between both streams.