Varnish looks very, very awesome. I already have Nginx installed, but the caching options for Nginx seem dizzy to me or I have read wrong pages. Varnish seems very solid and has great reviews about its capabilities. Good thing my server has 5 IPs…and only 2 are actively used. :) > Am 31.03.2015 um 16:36 schrieb Daniel Rinehart <[email protected]>: > > Yes to both: > > https://www.varnish-cache.org/docs/4.0/users-guide/vcl-example-websockets.html > > <https://www.varnish-cache.org/docs/4.0/users-guide/vcl-example-websockets.html> > > http://nginx.org/en/docs/http/websocket.html > <http://nginx.org/en/docs/http/websocket.html> > > > -- Daniel R. <[email protected] <mailto:[email protected]>> > [http://danielr.neophi.com/ <http://danielr.neophi.com/>] > > On Sat, Mar 28, 2015 at 10:46 PM, Kevin Ingwersen (Ingwie Phoenix) > <[email protected] <mailto:[email protected]>> wrote: > I am using Socket.IO over the same HTTP instance as my Express app. Does a > reverse proxy like Varnish or the NGINX method support that? > >> Am 28.03.2015 um 23:01 schrieb Daniel Rinehart <[email protected] >> <mailto:[email protected]>>: >> >> A common option to put a caching HTTP reverse proxy in front of node and let >> that handle all of the caching logic. Varnish Cache and NGINX Content >> Caching are popular options. >> >> -- Daniel R. <[email protected] <mailto:[email protected]>> >> [http://danielr.neophi.com/ <http://danielr.neophi.com/>] >> >> On Fri, Mar 27, 2015 at 9:15 AM, Kevin Ingwersen (Ingwie Phoenix) >> <[email protected] <mailto:[email protected]>> wrote: >> Hey everyone! >> >> My current project is based on using Express - or connect, still trying out >> which is better… - and serves a good amount of static files that are likely >> to not change in a long time during production. >> >> But the current cache-hell that I have is pretty … ugly. I mean, just look >> at this: >> >> http://git.ingwie.me/ingwie/bird3/blob/master/lib/request_handler.js#L59 >> <http://git.ingwie.me/ingwie/bird3/blob/master/lib/request_handler.js#L59> >> >> Isn’t there a MUCH easier solution than the way I chose? I want to be able >> to cache all the served images, css, js and oj scripts in the browser…but >> how can I do it „right“? This just looks like a big mess to me really...
-- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/2E0FA596-5B09-49DA-9BBD-1335EE888511%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
