projects / platform / upstream / nodejs.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 36a45c4) | patch
Throwing in a callback should kill the process
authorRyan Dahl <ry@tinyclouds.org>
Thu, 20 May 2010 22:21:40 +0000 (15:21 -0700)
committerRyan Dahl <ry@tinyclouds.org>
Thu, 20 May 2010 22:23:36 +0000 (15:23 -0700)
commitcbd2c3945b1df5b538d9e257646f604d9189601c
tree14ea543b288043feb8edf55f9cba37f666e73f6atree | snapshot
parent36a45c4e0def497e3d1446057c1d91680d8bb259commit | diff
Throwing in a callback should kill the process

There is a difference between errors which happen to a socket - like
receiving EPIPE - an exceptional situation but ultimately okay and the
situation where code throws in a callback - which is not okay.

Fixes test/simple/test-http-exceptions.js

TODO: explain this in docs.
lib/http.js diff | blob | history
lib/net.js diff | blob | history
src/node.js diff | blob | history
src/node_http_parser.cc diff | blob | history
test/simple/test-http-upgrade2.js diff | blob | history
Domain: Web Framework / Common;