Instead of messing with process._eval I decided to find where node starts
the main code. Turns out things work fine if you add the clustering code in
`lib/module.js`'s runMain function.
On Tuesday, September 30, 2014 11:55:12 PM UTC-5, Adam Snodgrass wrote:
I'm currently working on a project
Hello,
Hi,
I would like my next web project to use Node.js and MongoDB.
I've spent the last several weeks downloading, running, and playing around
with pretty much all of the popular frameworks.
I think I finally figured out the direction I want to take but I'm having
a hard time
I would like to know how exactly parallel execution works.
I'm using nimble module to execute some functions in parallel, and the
result of those executions be used for a final calculation. When I run
flow.parallel what exactly happens ? I mean, is it created a thread for
each function ? those
There is a good MySQL driver for node in npm. It would be more accurate to say
that mongodb is suited to node because it has an API that is based on
JavaScript to begin with. But node isn't any worse at MySQL than other
frameworks.
--
Job board: http://jobs.nodejs.org/
New group rules:
On Oct 1, 2014, at 7:06 AM, Kleyson Rios kleys...@gmail.com wrote:
I would like to know how exactly parallel execution works.
I'm using nimble module to execute some functions in parallel, and the result
of those executions be used for a final calculation. When I run flow.parallel
what
Unless someone has access to the server, they should not be able to view
the server's source at all.
If you are finding that your files are being transmitted, I would look at
how you are setting up your server. Either the reverse proxy you are using
is serving your whole application
...And after hitting post I realize this question has a ton of answers,
sweet!
On Wednesday, October 1, 2014 2:06:01 PM UTC-5, Albert Engelbrecht wrote:
Unless someone has access to the server, they should not be able to view
the server's source at all.
If you are finding that your files
