On Thursday, March 24, 2016 at 7:51:35 AM UTC+5:30, Matt Sergeant wrote:
>
> On Wed, Mar 23, 2016 at 12:25 PM, Harry Simons > wrote:
>
>>
>> For example, if an isolated and primarily an I/O bound request takes,
>> say, 3 seconds to get serviced (with no other load on the
> Does that answer your questions?
Thanks Ben, for taking the time to write. I did find your response (and
Matt's too) both interesting and enlightening.
> > Node.js uses non-blocking I/O when it can and only falls back to a
> > thread pool when it must.
So, like file-system I/O, what
Hello Harry, replies inline.
On Wed, Mar 23, 2016 at 5:25 PM, Harry Simons wrote:
> Hello,
>
>
> I have not been able to see the following points addressed in all the online
> material I have read to date on Node, and so, hope to be enlightened by some
> very smart and
As I understand it, a package author can un-publish their package on
npmjs.com, and somebody else can publish a package with the same name. If I
create a package depends on a package from npmjs.org, I have little
protection against a "bait-and-switch" which could result in unwanted, even
It's starting to sound like you haven't even tried building anything yet.
Write some code, try it out. We don't know if the suggested libraries will
be enough for you until you actually come back with something more than a
vague question. Sorry to be harsh, but you need to code something up
On Wed, Mar 23, 2016 at 12:25 PM, Harry Simons
wrote:
> Hello,
>
> I have not been able to see the following points addressed in all the
> online material I have read to date on Node, and so, hope to be enlightened
> by some very smart and knowledegable folks here that I
Hello,
I have not been able to see the following points addressed in all the
online material I have read to date on Node, and so, hope to be enlightened
by some very smart and knowledegable folks here that I presume would be
reading this.
1. Since I/O happens asynchronously in worker
Have you tried listening for "exit" in addition to "SIGINT" and
"uncaughtException"?
process.on('exit', (code) => {
// do something
});
-Original Message-
From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf Of
Atnakus Arzah
Sent: Tuesday, March 22, 2016 10:30