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 app that does conversion in background with kue's default UI, a fixed number of conversion is allowed to reduce the cpu load, the rest has to be in queue. Am I correct? question, how #1 sends job to #2? Thanks, Angelo On Feb 4, 7:50 pm, Felix Geisendoerfer <haimu...@gmail.com> wrote: > Use a queue: I'm partial to redis-based queue implementations > likehttps://github.com/technoweenie/coffee-resque > orhttp://learnboost.github.com/kue/, but anything that will allow you to > asynchronously process varying workloads with minimal overhead is fine in > my book. > > PS: I still have nightmares from the last time I used CentOS, but YMMV : ). -- 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 subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
