[Unbound-users] concurrent processing of queries from the same TCP connection

[Zi Hu]

Hi,

I noticed that when unbound processes queries from the same TCP connection,
it processes them sequentially.

If I send multiple queries over the same TCP connection, unbound processes
them one by one (not concurrently), which causes head of line blocking: The
later queries have to wait previous queries to get processed.

The question is:
Is there any particular reason that unbound doesn't support concurrent
processing of queries from the same TCP connection?


thanks
-Zi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20131217/653c6195/attachment.htm>