はてなブックマーク

In this post, I take a look at the different patterns that you need to know when using Node.js. These came from my own coding and from a look at the code behind Tim Caswell's flow control libraries. I think it is necessary to know how these basic patterns are implemented even if you use a library.. 1. Objects and classes 1.1 Class pattern // Constructor var Class = function(value1, value2) { this.

I've spent some time recently figuring out the options for deploying Websockets with SSL and load balancing - and more specifically, Socket.IO - while allowing for dual stacks (e.g. Node.js and another dev platform). Since there seems to be very little concrete guidance on this topic, here are my notes - I'd love to hear from you on your implementation (leave a comment or write about and link back

The first basic thesis of node.js is that I/O is expensive:  So the largest waste with current programming technologies comes from waiting for I/O to complete. There are several ways in which one can deal with the performance impact (from Sam Rushing): synchronous: you handle one request at a time, each in turn. pros: simple cons: any one request can hold up all the other requests fork a new proc

What does this code print out? Assume that console.log logs to the console. Experiment #1: For loop console.log('For loop'); for(var i = 0; i < 5; i++) { console.log(i); }0, 1, 2, 3, 4 - easy, right? What about this code? Experiment #2: setTimeout console.log('setTimeout'); for(var i = 0; i < 5; i++) { setTimeout(function() {console.log('st:'+i)}, 0); }The result is 5, 5, 5, 5, 5.What about