I am using node in Windows environment.
When I use fs.unlinkSync(fileName), it seems to work.
After the unlinkSync statement is executed, if I do a
fs.existsSync(filename) it returns false indicating the file does not
exists but when I go to the physical drive I could still see the file.
At this
On Thursday, December 26, 2013 11:34:54 PM UTC-5, Dmitri Zaitsev wrote:
>
> I have what looks like successful karma installation, yet karma is not
> in /usr/local/bin/ and is not found by bash.
>
>
Probably because there is no "bin"[1] set for that npm package.
[1]
https://github.com/karma-runne
I have what looks like successful karma installation, yet karma is not
in /usr/local/bin/ and is not found by bash.
Here are the end installation messages:
> ws@0.4.31 install
/usr/local/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebu
Now twoside.js is upgraded to 0.1.7. A initial big bug, which had been
prevented it working on node.js, was fixed in earlier version. After
testing it with karm test runner in client side, mocha test framework on
server side, I have used it on my own project successfully. Now I have
forgotten
Just entered in my radar, today:
https://github.com/OptimalBits/bull
It uses redis for persistence.
Each queue has name, redis server, redis port.
And you can send any message to a named queue
And process any message from a named queue, I suppose from any machine that
can access redis server.
This one souds good too...there is a plenty of lines like this on the page
you posted...
console.log(res); // { data: [ { name: 'Ricky Bobby' } ] }
On my example..I've a line like this with responses like this too..I am not
able to fetch row by row..if you know how to solve this...plz come ba
At my last company we had good success with coffee-resque backed by Redis
with a little custom coding around it. Each worker was an independent
process that was managed and kept alive with node-foreman and monit. Jobs
added to the queue included a timeout that the worker used to trigger
timeouts al
Sorry, I don't know how to express in more detail.
But the async is at FE server, something like
sendtask(task, function (err, result) { ... .});
The task (maybe a simple javascript object, serializable to JSON), goes to
the task queue, and the callback is assigned to task id.
If the response q
How does this fit in NODE.JS??
What you describe does, not seem like async programming at all to me...
Angel Java Lopez escreveu:
>I prefer
>
>Available worker pulls task
>
>over
>
>Available worker is notified
>
>The first one could use a queue, as you mentioned. So any other process
>(a
>prog
I prefer
Available worker pulls task
over
Available worker is notified
The first one could use a queue, as you mentioned. So any other process (a
programmer, a supervisor program, etc...) can launch workers, and the
workers only need to know:
- The queue having pending tasks
- Maybe a queue wh
Thank you for your answer Marco.
I found this package which seems to be working great for now
https://npmjs.org/package/facebook-complete
cheers
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this
11 matches
Mail list logo