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
_______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
