28 August, 2014, 09:38 AM
It seemed to me that every web coder in San Fransico is using Node.js and I thought that I should find out what it is in case I am missing the boat on something.
And to output text to the console use the console.log("text"); function.
It comes with various modules such as for file handling or http requests which you load as required.
A benefit of Node.js as a server is that it encourages the use of Asynchronous data transfers so that the server can be bombarded with requests for data without "blocking" i.e. it doesn't have to wait for each data request to be served in sequence which could create a bottle-neck if some data servers are slow to respond. This contributes to the goal of having responsive single-page apps.
In conclusion: for most webmasters, I think it is a curiosity and only of serious interest to developers of bespoke Intranet Solutions for corporate clients. But I could be wrong
28 August, 2014, 14:12 PM
Hmm, a front-end JS single-page framework should use asynchronous data requests normally, so why does the server have to do asynchronous database requests? Only if it is operating in a distributed server environment maybe (where the servers take various significant times to respond)?
28 September, 2014, 12:55 PM
Boo hoo, Node body liked my post!
Tags for this Thread