The fix which makes the GoogleClosure processor thread-safe has a side-effect
which prevents the processor for being used in parallel. When two resources
needs to be processed in the same time, these are executed sequentially.
The purpose of this task is to improve the processor implementation and to make
it possible to process resources asynchronously. A possible solution would be
using a pool of googleClosure compilers.
Original issue reported on code.google.com by alex.obj...@gmail.com on 12 Aug 2012 at 12:07
Original issue reported on code.google.com by
alex.obj...@gmail.comon 12 Aug 2012 at 12:07