superjoe30/node-multiparty — pull request #19 by luman75 (2013-09-23 17:17:49+00:00)
Title: Throwing the aborted exception seems to be unnecessary. 

Throwing the aborted exception seems to be unnecessary
In addition to that it's difficult to catch it in a real application.

If the client aborts the connection I'm receiving many exceptions like this:
Unhandled exception AssertionError: Error: Request aborted
at IncomingMessage. (node_modules/multiparty/index.js:93:17)
at IncomingMessage.EventEmitter.emit (events.js:92:17)
at abortIncoming (http.js:1881:11)
at Socket.socket.onend (http.js:1973:7)
at Socket.g (events.js:175:14)
at Socket.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:910:16
at process._tickCallback (node.js:415:13)
stack: AssertionError: Error: Request aborted