From 8139bb24c1f72cdea41492bf3bf395a66e04104f Mon Sep 17 00:00:00 2001
From: Ryan Dahl <ry@tinyclouds.org>
Date: Mon, 11 Oct 2010 16:36:12 -0700
Subject: [PATCH] Add destroy methods to HTTP messages

needs tests (particularly for pipeline situations)
---
 lib/http.js | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/lib/http.js b/lib/http.js
index 1385e4272c..939d2c3b4f 100755
--- a/lib/http.js
+++ b/lib/http.js
@@ -210,6 +210,12 @@ function IncomingMessage (socket) {
 util.inherits(IncomingMessage, stream.Stream);
 exports.IncomingMessage = IncomingMessage;
 
+
+IncomingMessage.prototype.destroy = function (error) {
+  this.socket.destroy(error);
+};
+
+
 IncomingMessage.prototype.setEncoding = function (encoding) {
   var StringDecoder = require("string_decoder").StringDecoder; // lazy load
   this._decoder = new StringDecoder(encoding);
@@ -303,6 +309,12 @@ function OutgoingMessage (socket) {
 util.inherits(OutgoingMessage, stream.Stream);
 exports.OutgoingMessage = OutgoingMessage;
 
+
+OutgoingMessage.prototype.destroy = function (error) {
+  this.socket.destroy(error);
+};
+
+
 // This abstract either writing directly to the socket or buffering it.
 OutgoingMessage.prototype._send = function (data, encoding) {
   // This is a shameful hack to get the headers and first body chunk onto