Maintained by: NLnet Labs

[Unbound-users] unbound wrapper in Go

W.C.A. Wijngaards
Tue Jul 3 09:03:02 CEST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Tony,

On 07/02/2012 05:17 PM, Tony Finch wrote:
> W.C.A. Wijngaards <wouter at nlnetlabs.nl> wrote:
>> 
>> Yes, on purpose, since this reply is from a unix-pipe, the ID
>> field does not have to be used.
> 
> I thought that DNS responses do not have to come in the same order
> as requests, even over stream connections.

Actually, stream responses could be like that, but I would not know
how backwards compatible with the deployed software that would be.
Unbound serves stream responses in the order they have been queried
for that reason.

This reply we talk about here is an internal pipe in the
implementation of libunbound, and another field is used to
disambiguate it (libunbound could support more than 64k concurrent
queries, therefore it does not use the 16bit ID value).

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJP8pkhAAoJEJ9vHC1+BF+NMPsP/joiLiWcYdN5H4eYo7ryxstb
ek+nP48mqDkbguMBsj/WlS1dcm3ooqX+VDUVIr6BoKEg+BmcdQ3Pgm7sXQ/fJ35m
IjPLwtvNz0nOnYUYWsrr9pRqOi/QE2Mz+PDcytuxUNAiZkbTBfYleiKBAZJtJK4B
e5rTAE4VGcz7f+0EQAolYbAf5HhjHfVEKcOV5pn4lmNObAxMg9k5R7tzQevgmNN5
indDXtuNH+0G4RRMn2FWRxgf2yIdoMBcmUBZqYPlYIYxGYu3mMlkCYeEw6o+Am+O
22NeO0AD+HkRBl+mT0AsERqSWMpCi/1jjuS6UaHdQSMy1zmj9gowSCRnpi6t90GT
o37BMpOIXl6xsKF5MHKaiHy9xnk4jl/MIEgVa+CMWKeP9uLotnw1DyTD0Feq7aNf
Hd/Qvff7iG+hAq7vMR3a4il/tAWm3gMpAL+9ju5pK9zppcDJPToeHkTYt50hDLis
n4X2h+zPoqC+7hz61vW9RzJzUBEipxtPNfDdcMdDRCpp3y22ue1sBa8XssYY4hb9
dy3HEL9lKBxrRWLyHxLWjZ6dQnZUhwbOqAlTMvqhrCNuT+dzL8RYIAxsAguSyIq9
iGfgCkL3VCpkGtErdTsWMQmgQUvQIwOW84Mlrk562eAcRs1IHjbwwR/nV+Q39Hux
/BwMI4lKLy02Ao+u/GB5
=o6eO
-----END PGP SIGNATURE-----