On Tue, Jul 22, 2014 at 5:29 PM, Daniel Lintott wrote: > I would say that seems like a sensible suggestion. Using a ready-made > system for the caching obviously has major benefits of being > well-established and supported. > > Personally I've never used or setup such a service, but there are > several available: nginx[1]; trafficserver[2]; haproxy[3]
I expect we will just go with mod_cache from apache2, seems the simplest option. > I shall drop another version of the patch to the bug report that reverts > the custom caching mechanism. A yak shaving exercise reminded me that this hasn't been done yet, could you please send the updated patch? -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6FcABA=CQYd+6Dc+vKE9r5zVCXS1SZGvELyRG2i=2o...@mail.gmail.com
