Thanks Stephen, Thanks for the reply! So it sounds like it works somewhat like a cloud server. Excellent! Thank you for the link to ESI, I've never heard about it before.
Best, Anton On Thu, May 2, 2013 at 1:16 PM, Stephen Wood <[email protected]> wrote: > Generally, you set the TTL on objects based on how frequently they update. > You can also manually send a purge or force refresh objects if you know > they've been updated. > > If your application includes a mixture of static and dynamic content, you > can read up on ESI<https://www.varnish-cache.org/docs/3.0/tutorial/esi.html> > . > > > On Mon, Jan 14, 2013 at 7:52 AM, Anton Soradoi <[email protected]>wrote: > >> Hi, >> >> I've found a link to the site on HN and got very curious in what you have >> to offer. >> >> My only concern is how does Varnish deal with frequent resource updates? >> (The company I work for has a website that it is being actively >> developed, with it's resources being updated multiple times a week. I.e js >> files, css files, images often need refreshing) >> >> Disclaimer, I have not read up too much about Varnish, so a quick answer >> would suffice. >> >> Thanks! >> Anton >> >> _______________________________________________ >> varnish-misc mailing list >> [email protected] >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> > >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
