umbrant/non-blocking-buffers

Lock-free message passing over shared memory for a single producer and consumer

non-blocking-buffers's Issues

Multiple channels per process

Right now, processes using the NBB have an array of length NUM_CHANNELS, of which only the first is actually allocated or used (in init_service or get_channel). This needs to work with multiple channels, and depends a bit on having a real nameserver.

Initial nameserver implementation

The nameserver needs to dish out shared memory IDs to services and clients, so they can connect up. Right now, it's just a header file with some #define's in it. There needs to be a bit of thought on the initial "connect to nameserver" protocol, the mapping between services and shared memory IDs, and which shared memory IDs to give to a channel when a client tries to connect to a server.

This might be a big one, so make more issues as you go.