diff --git a/test/test-http.js b/test/test-http-server.js similarity index 98% rename from test/test-http.js rename to test/test-http-server.js index c8e05bb8cb..59300cf284 100644 --- a/test/test-http.js +++ b/test/test-http-server.js @@ -1,6 +1,6 @@ include("mjsunit"); -var port = 8000; +var port = 8222; function onLoad() { diff --git a/test_client.js b/test_client.js index 56fe6acf94..ddd1d48600 100644 --- a/test_client.js +++ b/test_client.js @@ -1,11 +1,12 @@ var c = new node.http.Client(8000, "localhost") -var req = c.get("/hello/world", [["Accept", "*/*"]]); +var req = c.get("/bytes/123", [["Accept", "*/*"]]); req.finish(function (res) { puts("response 1: " + res.status_code.toString()); res.onBody = function (chunk) { - puts("response 1 body <" + chunk.encodeUtf8() + ">"); + chunk = chunk.encodeUtf8(); + puts("response 1 body <" + JSON.stringify(chunk) + ">"); return true; }; @@ -15,19 +16,21 @@ req.finish(function (res) { }; }); -/* -var req = c.get("/something/else", []); -req.finish(function (res) { - puts("response 2: " + res.status_code.toString()); +setTimeout(function () { + var req2 = c.get("/something/else", []); + req2.finish(function (res) { + puts("response 2: " + res.status_code.toString()); - res.onBody = function (chunk) { - puts("response 2 body <" + chunk.encodeUtf8() + ">"); - return true; - }; + res.onBody = function (chunk) { + chunk = chunk.encodeUtf8(); + puts("response 2 body <" + JSON.stringify(chunk) + ">"); + return true; + }; + + res.onBodyComplete = function () { + puts("response 2 complete!"); + return true; + }; + }); +}, 2000); - res.onBodyComplete = function () { - puts("response 2 complete!"); - return true; - }; -}); -*/ diff --git a/website/node.html b/website/node.html index 488f864124..2226393ab6 100644 --- a/website/node.html +++ b/website/node.html @@ -225,10 +225,14 @@ See node.http

Node provides a web server and client interface. The interface is rather -low-level but complete. For example, it does not parse -application/x-www-form-urlencoded message bodies. The interface -does abstract the Transfer-Encoding (i.e. chuncked or identity), Message -boundaries, and Keep-Alive connections. +low-level but complete. (By complete, I mean that it does not limit you from +any of HTTP's features.) The interface abstracts the Transfer-Encoding (i.e. +chuncked or identity), message boundaries, and persistent connections. +Message header and body parsing needs to be done in high-level abstractions. + +

There are even lower level versions of both the server and client. You +very likely do not need the level of granuality provided by them. There are +no docs for those interfaces.

node.http.Server