On Mon, Aug 6, 2012 at 6:15 AM, tjholowaychuk <[email protected]> wrote: > Don't cache with node, slap varnish in front
I wonder whether Nodejitsu is using something like that. And I wonder how Varnish will know whether a file has changed and its cache needs to be updated. With `Cache-Control: no-cache`, I assume Varnish needs to get an up to date file for *every request*. Then, again, there would be a read operation from disk per request, and exactly that I want to avoid. > node-static does it extremely wrong and will give you stale responses > and invalid ones at times depending on the request Why is that? Eventually I consider watching the source code in `scripts` and - on change - have it minified to `xyz.js`, or in memory. Oliver's node-filecache looks interesting for that purpose. -- 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
