Hi Felix,
Thanks for the reply, the app is only for a local network, not to be
in the public net, need only a simple solution. your kue idea is good,
if i understand it correctly, there will be two node apps:
1) the node web app that accepts file upload, then send over to #2
2) node/kue based
Hi,
how to use coffee-resque in a project? it does not have npm install
option. I tried following:
1. app.js
2. create a node-modules and copy the entire coffee-resque under it
3. in coffee-resque i did a : make generate-js
in the code:
var resque = require('coffee-resque').connect({
host:
How the queue is managed is up to you, really. You could run a queue
server like redis, rabbitMQ, etc. or even use a shared folder on NFS
that you rename files into and out of. If there's only ever one
worker machine you probably skip setting up a separate message queue
server and just manage
Hi,
Is there a sample code that shows how to use coffee-resque? the one in
github seems not enough ? Thanks,
Angelo
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are
On Sun, Feb 5, 2012 at 2:02 AM, Angelo Chen angelochen...@gmail.com wrote:
hi,
trying out with kue:
npm install kue
got :
npm http 408 https://registry.npmjs.org/cssom/0.2.0
npm ERR! registry error parsing json
npm WARN cssom@0.2.0 package.json: bugs['web'] should probably be
Realizing that Globals is actually quite low-level I think it would be
useful for caching data and web session storage. Since it's not a
network service it doesn't actually replace redis or memcached out of
the box but you could wrap it with your own node.js server to provide
a shared web
Hi,
Thanks to all who answered my newbie's question, it helps me finally
implemented a working solution, all suggestions are correct, what I do
is:
use coffee-resque to convert one image at one time, it works quite
well in a old Pentium 4 box, and the program is still very responsive,
learnt a
25k seems a little expensive :) Just kidding.
Great job, judging the book by its cover it looks pretty professional.
Hope this gets lots of people interested in node.js in korea!
Nuno
On Sun, Feb 5, 2012 at 4:06 PM, Outsider outside...@gmail.com wrote:
I'm Korean programmer like node.js.
I met a following strange issue on nodejs v0.6.6
My application use a lot of http.get() calls. When node handles
multiple requests for a while (after process 10k - 50k requests), it
crashes on node.js:201.
I have put try...catch... on http.get, but no luck, the error can't be
captured and node
I pipe each process's stdout and stderr into separate files. Then I have a
script that tails all files at once. I put a prefix on each line telling
what process is issuing the line. So ...
- I can watch the output from all processes in one tty window
- I rotate the files as logs.
- when
On Sun, Feb 5, 2012 at 12:49 PM, Martin Cooper mfncoo...@gmail.com wrote:
On Sun, Feb 5, 2012 at 5:04 AM, Mark Volkmann r.mark.volkm...@gmail.com
wrote:
On Sat, Feb 4, 2012 at 10:27 PM, Martin Cooper mfncoo...@gmail.com
wrote:
On Sat, Feb 4, 2012 at 8:01 PM, Mark Volkmann
AFAIK the http RFC section 9.1.2 actually does state that delete is
idempotent. Now we all know that idempotency is about the state of the
resources and not how the server here there. So yes I was being a smart
ass. ;)
On Feb 5, 2012 8:44 AM, tjholowaychuk tjholoway...@gmail.com wrote:
On Feb 5, 11:45 pm, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Sun, Feb 5, 2012 at 21:11, Bert Belder bertbel...@gmail.com wrote:
10060 WSAETIMEDOUT
Connection timed out.
A connection attempt failed because the connected party did not
properly respond after a period of time, or the
yep, it's GETting /favicon.ico.
this has gotten me before, it is really irritating.
On 2/5/12, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Sun, Feb 5, 2012 at 23:43, Mark Volkmann r.mark.volkm...@gmail.com
wrote:
Here's a very simple HTTP server:
var http = require('http');
Another thing chrome does...
This isn't just chrome. Every browser since the 90s automatically
requests /favicon.ico.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are
Ok I just tagged and published v0.0.1 of node-gyp on npm.
Here is the repo: https://github.com/TooTallNate/node-gyp
Native addon devs, please try it out and begin migrating your module to
using gyp. Let me know about your results!!
On Fri, Feb 3, 2012 at 11:13 PM, rhdoenges rhdoen...@gmail.com
Hi,
I just heard the cast, and I was quite happy that you are talking about
a theme I'm still struggeling with: build tools (continue the discussion
on this on this topic:
https://groups.google.com/group/nodejs/browse_thread/thread/9814da6a8873db2f/fdfaefa8ca5db7aa
)
First off: Please check the
Yeah, of course. But browserify does this better as anything else, and
it's IMO the most important part of the JavaScript build process. So a
lot of focus should go on this and every single nodejs build tool should
support it by default.
Just specifying one file to start this assembly and then
On 5 February 2012 00:50, Felix Geisendoerfer haimu...@gmail.com wrote:
Use Amazon S3 as a temporary file system: When you get a new file, put it
there (use reduced redundancy if you want to save costs), then let the
workers pull the file from S3. You will thank yourself for doing this when
it
Wow, that looks really cool.
The readme doesn't mentioning actually creating a gyp file. You still
have to do that, right? It'd be nice to document what it should look
like.
On Sun, Feb 5, 2012 at 19:15, Christopher Jeffrey chjjeff...@gmail.com wrote:
Works well for me, very painless. I hope
Marcel,
I wrote a simple code with 12 lines to read newly added lines of a file
when changes happen, as you do in the previous sample.
https://gist.github.com/1750489
However, it couldn't read newly added data (Node v0.6.9, macOS X).
Is something wrong with my code?
How can your code work
21 matches
Mail list logo
