Changes between Version 2 and Version 3 of Ticket #11649, comment 28
- Timestamp:
- Jan 9, 2014 11:57:36 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11649, comment 28
v2 v3 8 8 9 9 I think this issue could be related to nodejs' non blocking I/O architecture. What happens (at least I think this is what happens) is that npm asks very fast for multiple DNS entries and queueing the answer in a callback. So we get multiple simoultaneously DNS requests although the answer hasn't arrived yet. 10 What thescript does is (if I read that correctly) opening sequently 100 dns queries and *waiting* for the reply before opening another.10 What your script does is (if I read that correctly) opening sequently 100 dns queries and *waiting* for the reply before opening another. 11 11 Could this be right? 12 12