Though if you are going to cache with node you'll have to do a better job than the hack I did with staticCache(), node-static does it extremely wrong and will give you stale responses and invalid ones at times depending on the request
On Sunday, 5 August 2012 21:14:37 UTC-7, tjholowaychuk wrote: > > Don't cache with node, slap varnish in front > > On Friday, 3 August 2012 07:46:37 UTC-7, Felix E. Klee wrote: >> >> What is a good module to serve some static (JavaScript) files (including >> caching and compression)? >> >> Desired mapping of files to URLs: >> >> scripts/*.js -> http://example.com/scripts/*.js (only for development) >> xyz.js -> http://example.com/xyz.js >> app.js -> not served (of course) >> package.json -> not served (of course) >> ... >> >> That's it. There is no public directory in my app. >> >> What I already looked at: >> >> * node-static: only allows specification of a public directory which is >> mapped to the root of <http://example.com/>. As you can see above, >> this is not what I want. >> >> * connect: will not do caching anymore ("connect.staticCache() is >> deprecated and will be removed in 3.0 use varnish or similar reverse >> proxy caches") >> >> By the way, I plan to deploy to Nodejitsu. Does anyone know whether they >> do automatic caching? >> > -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
