What sort of work/connections are you talking about here? Are you talking
about processing AMQP messages in a thread pool or are you talking about
writing some sort of multithreaded I/O handler?
On Thu, Apr 30, 2015 at 2:47 PM, Alan Conway <acon...@redhat.com> wrote:
> Can the proton reactor be used to deliver work from multiple connections
> to a thread pool, where work from a given connection is only handled by
> one thread at a time (so access to each pn_transport and it's stuff is
> serialized)? That is a pretty standard model for servers.
> It doesn't look to me like this is the case but I may be missing
> something. If it is the case, what's the pattern for doing it?