FIrst and second request get different filenames

Hello,

Brilliant work! Thank you! I installed and have it successfully setup on a development server. I note in the logging that the hash filename for the css is different from the first request to the second. After that it is fine. I know that this is likely during the creation of the file and, to save time, you are sending the file on-the-fly during the first request but I guess I expected you'd use the same hash to save the file in the cache directory. Not very good at coffee script here so I am not sure where this behavior is being introduced. Thanks, again.

[dmauro]

Hi, Bret. Sorry I didn't get a chance to look into this yet, but if you
have a GitHub account, would you mind opening an issue for this here:
https://github.com/dmauro/node-jade-compress/issues?sort=comments&state=open

It would help me out in keeping track of this and making sure I address it
as soon as I have some spare time. Thank you very much!

-Dave

On Sun, Sep 22, 2013 at 4:39 PM, Bret notifications@github.com wrote:

Hello,

Brilliant work! Thank you! I installed and have it successfully setup on a
development server. I note in the logging that the hash filename for the
css is different from the first request to the second. After that it is
fine. I know that this is likely during the creation of the file and, to
save time, you are sending the file on-the-fly during the first request but
I guess I expected you'd use the same hash to save the file in the cache
directory. Not very good at coffee script here so I am not sure where this
behavior is being introduced. Thanks, again.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6
.