Closed palpha closed 13 years ago
I'm not very familiar with IIS, but why is it necessary to build caching and compression into the CoffeeScript handler? Aren't there other handlers that are specially build for this task and are better at it?
There probably are, but all examples I've encountered are code examples to roll your own. But you're right, the caching stuff is outside your project's scope. Close and forget about it :).
Also, Jurassic isn't thread safe, thus the ThreadStatic business. Use if you'd like to, I tried to follow your formatting. However, I was unable to figure out why it takes over a minute to fire up the CoffeeSharpEngine, so I have to abandon this for the time being.