Re: IBM announces new language environment - Node.js for i

a websockets server is not a http server it a socket server that just serves
the headers with HTTP

On Tue, Oct 7, 2014 at 8:10 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I'm not an expert, but I seem to recollect a web sockets example using

node.js where it built it's own web server and it didn't seem to be a lot
of code.


var http = require("http");
var url = require("url");

function start() {
function onRequest(request, response) {
var pathname = url.parse(request.url).pathname;
console.log("Request for " + pathname + " received.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello World");
response.end();
}

http.createServer(onRequest).listen(8888);
console.log("Server has started.");
}

exports.start = start;

---

A tutorial would explain it. But you're right. There isn't a need for a lot
of code to create an HTTP server, which is somewhat different than a Web
socket server. And that's part of the appeal of the language / runtime
environment.

That example both creates an HTTP server instance for handling the sockets
and protocol, and responds with simple content.

Nathan.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.