Re:Node.js for Server Noobs
by points on Friday September 03, 2010 @06:52PM
(#1661415)
19 people upvoted this? Did you even check? It has 0 content.
The 'meat' of the "article" is
webby# curl -O http://nodejs.org/dist/node-v0.2.0.tar.gz
webby# tar xvzf node-v0.2.0.tar.gz
webby# cd node-v0.2.0
webby# ./configure
webby# make
webby# make install
Which I think most people who can read docs can work out.
and then debugging paths, dependencies, realizing after 20 minutes of compilation that they're actually missing a module, editing php.ini and calling the president.
It's cool that articles like these actually highlight how easy deployment can be with Node. Thanks DTrejo!
Re:Node.js for Server Noobs
by DTrejo on Friday September 03, 2010 @07:26PM
(#1661489)
I did say it was for noobs.
Main useful bits:
* cheap host, $10/month, root access so no configuration headaches. My search didn't turn up many of those, and the node hosting wiki page is non-obvious: http://github.com/ry/node/wiki/Hosting/_edit (and only just added webbynode to the list)
* how to set up that machine in particular
* points to other helpful resources once node is installed
Re:Node.js for Server Noobs
by c00p3r on Saturday September 04, 2010 @12:10AM
(#1661991)
btw, it is time to put the support for clang++ in V8's scons build system. It is not obvious what file should I modify. In the case of a traditional make I just redefine one environment variable before doing ./configure or modify one variable in a Makefile (clang is compatible with gcc's command line arguments).
Re:Node.js for Server Noobs
by mahmud on Friday September 03, 2010 @11:47PM
(#1661953)
Do you have an specific SOAP API in mind, or do you want a generic "SOAP sink" powered by Node? If the former, you can get away with your own lousy in-house implementation (2 pages of javascript, really.) If you want a full blown SOAP client implementation, including WSDL parsing, you better hope there exists something already.
My recommendation, as the developer of a SOAP client/server library; don't bother. Use Java or PHP, as those have the best SOAP libs out there, and figure out a way to pipe SOAP requests through your own java/php "proxy" app and let those libs take care of the cruft.
Using Node for SOAP is sacrilege. The two are diametrically opposed in their philosophies, and SOAP will easily negate any performance gains you might have made from using an event-drive server.
Re:Node.js for Server Noobs
by White_N_Nerdy on Saturday September 04, 2010 @02:19PM
(#1663100)
Thanks for the advice. I just wanted to use Node as a way of "pushing" events down to the browser, but the only way Node will know if an event has happened or not is by polling a particular SOAP service. I do own the SOAP service though, so I suppose that I could add a new interface and let Node just connect with TCP?
What's the standard way of doing RPC between Node an other types of services?
Re:Node.js for Server Noobs
by White_N_Nerdy on Saturday September 04, 2010 @02:55PM
(#1663170)
I got the answer on IRC. Basically, you either make your non-Node servers push events to Node.js using Http OR you use something like AMQP. browser -> node.js -> AMQP -> JEE and then JEE -> AMQP -> node.js -> browser.
The 'meat' of the "article" is
Which I think most people who can read docs can work out../configure --with-abc --with-xyz --with-123=/in/some/place --without-something-else --disable-module --without-this-thing --and-everything-is-inconsistent
and then debugging paths, dependencies, realizing after 20 minutes of compilation that they're actually missing a module, editing php.ini and calling the president.
It's cool that articles like these actually highlight how easy deployment can be with Node. Thanks DTrejo!
Main useful bits:
* cheap host, $10/month, root access so no configuration headaches. My search didn't turn up many of those, and the node hosting wiki page is non-obvious: http://github.com/ry/node/wiki/Hosting/_edit (and only just added webbynode to the list)
* how to set up that machine in particular
* points to other helpful resources once node is installed
I'd rather say: This is what people can work out without reading the doc. :-)
However, to be fair: The article links to various other articles which contain the "real" introduction, i.e. how to use node.js after it is installed.
If you want to do it all on one line, "apt-get update && apt-get upgrade" is the answer.
The && means "run the second command only if the first command completes without an error" .
My recommendation, as the developer of a SOAP client/server library; don't bother. Use Java or PHP, as those have the best SOAP libs out there, and figure out a way to pipe SOAP requests through your own java/php "proxy" app and let those libs take care of the cruft.
Using Node for SOAP is sacrilege. The two are diametrically opposed in their philosophies, and SOAP will easily negate any performance gains you might have made from using an event-drive server.
What's the standard way of doing RPC between Node an other types of services?