Thread:Extension talk:CentralNotice/Caching Overhaul - Frontend Proxy/Migration? & minor cleanup/reply


 * I'd like to see a single skin change, ahead of time, which can be used to deliver banners from the existing system. Then, we can toggle back and forth between banner providers without the cache purge overhead screwing with the experiment.

The experiment being? If we make more money from the new system? If we have removed the banner bump? Whilst I agree with adding a toggle switch; we will not be able to make meaningful measurements for months. At least 2; probably more like 3. (First month for natural page cache expiration, next to for cache epoch purging.)


 * It would be good to mention that the design presented here is meant to be trivially migrated to ESI when that is available, cos this is a huge win.

I would not describe this as trivial -- it still requires user side data. We can ESI deliver the initial default content only.


 * U are using "mincut" in a way that I have not seen before

Yes, bad terminology on my part. I really meant the set of disjoint unions over allocations.


 * "VCL" is the mini-language inside of varnish, so I think you mean "C library called from VCL".

You can write native C in VCL. It does not necessarily require a native library.