[zeromq-dev] IOCP

[Martin Sustrik]

Mikael,

> I’ve worked a bit with some of these techniques and asked around to
> several people I know locally and they all believe in using Shared
> Memory for larger messages and named pipes for smaller ones. One guy
> recommended a solution of having a shared memory block for the messages,
> creating an index on it and sending the index key over a named pipe for
> retrieval by the recipient.

Using shmem can be implemented as an optimisation in the future.

However, we still need some pollable mechanism to signal events (as 
opposed to data) between communicating processes. Which brings us back 
to implementing NamedPipes support, which in turn needs IOCP etc.

> But I am fairly certain he is using
> Boost::Interprocess for it so that is maybe not useful. I’ve so far
> gotten by with a Shared Memory solution (and it is very fast so far),
> but the locking has been hard to make work.

True.

Martin