Alan Conway wrote:
On Thu, 2007-08-23 at 10:02 +0100, Gordon Sim wrote:
The serializer as currently implemented has a dedicated thread per queue
that does the dispatch; the publisher simpling pushing its message onto
the deque.
Not so. The Serializer will continue dispatch in the calling thread
*unless* doing so might cause tasks to be processed out of order - i.e.
if there is already a thread doing a dispatch or there are already tasks
queued up. (If it doesn't its a bug.)
Sorry, imprecise language on my part. Andrew clarified what I meant;
i.e. as it is currently used in the queue.
What I think we need (and I think Andrew is working towards) is
to eliminate the serializer and make the queues themselves the only
serialization and handover point for thereads. Only at the queues do we
have the tools to do useful flow control.
Very much agree!
