Revert "http: make http.ServerResponse emit 'end'"

This reverts commit 790d651.

This makes Duplex streams unworkable, and would only ever be a special
case for HTTP responses, which is not ideal.

Intead, we're going to just bless the 'finish' event for all Writable
streams in 0.10

doc/api/http.markdown

@@ -321,17 +321,6 @@ passed as the second parameter to the `'request'` event.
 The response implements the [Writable Stream][] interface. This is an
 [EventEmitter][] with the following events:
 
-### Event: 'end'
-
-`function () { }`
-
-Emitted when the response has been sent. More specifically, this event is
-emitted when the last segment of the response headers and body have been
-handed off to the operating system for transmission over the network. It
-does not imply that the client has received anything yet.
-
-After this event, no more events will be emitted on the response object.
-
 ### Event: 'close'
 
 `function () { }`

lib/http.js

@@ -840,7 +840,7 @@ OutgoingMessage.prototype._finish = function() {
     assert(this instanceof ClientRequest);
     DTRACE_HTTP_CLIENT_REQUEST(this, this.connection);
   }
-  this.emit('end');
+  this.emit('finish');
 };
 
 
@@ -1780,7 +1780,7 @@ function connectionListener(socket) {
 
     // When we're finished writing the response, check if this is the last
     // respose, if so destroy the socket.
-    res.on('end', function() {
+    res.on('finish', function() {
       // Usually the first incoming element should be our request.  it may
       // be that in the case abortIncoming() was called that the incoming
       // array will be empty.