This is not a technical question (I'm quite clear about how the stuff
works). I also did some (Google) research before asking.
I'm just curious if there is a good reason that I just fail to see... I AM
aware that very obviously I am not the first person to think about this,
but I just could not
Sir, you did not understand my question :)
However, I don't see how I could possibly be clearer - which
definitely is MY shortcoming. So sorry.
On Wed, Dec 12, 2012 at 11:59 AM, greelgorke wrote:
> why? its the simpliest and most common way, that's it. passing by custom
> params has to be impl
CORRECTION, I take my last statement back, you DID add to the
conversation and I am a bad reader.
I had already considered the performance issue of having the API
functions not just call the callback, but also having to handle
OPTIONAL additional parameters, which in node.js might happen some
mill
if (stat.isFile()) {
> //fs.readFile(...)... WHICH FILE
> console.log(file); // This file
> }
> }
>
> var files = [
> "E:\\site.css",
> "E:\\stacks.txt",
> "E:\\Node",
> ];
>
> files.forEach(function (file) {
> f
Because I think it should, but it doesn't, see this issue I debugged in
node-imap today:
https://github.com/mscdex/node-imap/issues/452#issuecomment-122023433
Basically, calling socket.destroy() did not end the connection. I had to
add a socket.end() in front to make it work.
--
Job board: ht
socket.destroy() - is
> supposed to kill the socket as soon as possible.
>
> On Thu, Jul 16, 2015 at 11:49 AM, 'Michael Hasenstein' via nodejs <
> nod...@googlegroups.com > wrote:
>
>> Because I think it should, but it doesn't, see this issue I debugged i
