On June 21, 2013 at 1:27:05 PM, Ronan Lucio ([email protected]) wrote: Hi,
Thinking deeply about this I wonder if the problem would by "how to process it on-the-fly". If execute "lessc file.less" LESS works properly, but the problem is I can't base my solution on a save-to-disk solution because it would cause a kind of race-condition on high load. So I need that LESS processing happens on-the-fly. Any tip would be appreciated? Race conditions aren't inherent. You can use locking, or tap into the running task. If the task is already running, wait for it to call back and then serve the same result. (Or take advantage of that on POSIX platforms, renames are atomic: generate into a temp file, then swap it into place, renaming over the other one) -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
