Refreshing modified content

[Paulo Paracatu]

Hi,

I read somewhere about backend conditional requests, or GET IMS. As I
understand, that would be exactly what I need. I'd be able to set a low TTL
and yet keep the BW beetween backend-varnish low.

And sorry if I sound rude. :P

2010/12/16 Per Buer <perbu at varnish-software.com>

> Hi,
>
> On Thu, Dec 16, 2010 at 9:31 PM, Paulo Paracatu <paulo at aliancaproject.com>wrote:
>
>> If I understood it, the purging method isn't automatic, right? I'd need to
>> purge the content everytime it is modified.
>
>
> Hi,
> Nobody purges the cache manually. You get your CMS to purge the cache for
> you.
>
> This is kinda stupid... I host more than 10k sites, modifying files
>> everytime. If I set a high TTL, the backend will be happy and the webmaster
>> will be angry. If I set a low TTL, the webmaster will be happy, but the
>> backend will die. Plus, there is no point using a cache if the TTL is low.
>>
>
> It isn't stupid, computers don't have intuition and you have to actually
> tell them when you update data. If you can propose another way of getting
> the cache to magically purge itself of stale content please share it with
> us. :-)
>
> --
> Per Buer, Varnish Software
> Phone: +47 21 98 92 61 / Mobile: +47 958 39 117 / Skype: per.buer
> Varnish makes websites fly!
> Want to learn more about Varnish?
> http://www.varnish-software.com/whitepapers
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20101216/fc4d1f90/attachment-0003.html>