Reported here: http://groups.google.com/group/nodejs-dev/browse_thread/thread/9e063d0938f99879 Would be good to test this somehow...
… first read of a range read.
Made this test in response to this thread: http://groups.google.com/group/nodejs/browse_thread/thread/f82835007a277de2/ But Node appears to be working correctly.
rnewson found a good bug in keep-alive. we were only using the request headers we send to enable/disable keep-alive but when the server sends Connection: close we need to close down the connection regardless. I wrote up a patch the Robert verified makes all his test client code work now and I also added a new unittest for it.
…n't autodetect it.
to enable KQueue, rather than deciding based on the compiler version.
- Add test case for pumping from unreadable stream. - Document the sys.pump error handling behavior
(this also splits the file into upper "setup" and lower "startup" sections)
The main system is built upon this, and is optional, if only natives are used in application (eg. node-core). Natives not loaded into own context if NODE_MODULE_CONTEXTS=1. This have its inner logic, if natives are seen just as lazy-loaded parts of the core.