Re: Any inerest in Zlib pre-compressed HTML generator responses?

> On Aug 16, 2016, at 2:16 AM, Curtis Maloney wrote: > > On 16/08/16 09:10, Bobby Mozumder wrote: >> Hi, >> >> I also use generators for my views, and I use Django’s streaming views >> with my generators to stream responses, so that the web browser receives >> early

Re: Any inerest in Zlib pre-compressed HTML generator responses?

I’ll look into what it would take to make it a separate package, to make it more generic and usable by all. I was pushing for this to be part of the core to overcome Django’s “slow-by-default” impression. My first version of this site had access times in the several second range, and it took

Re: Any inerest in Zlib pre-compressed HTML generator responses?

On 16/08/16 09:10, Bobby Mozumder wrote: Hi, I also use generators for my views, and I use Django’s streaming views with my generators to stream responses, so that the web browser receives early responses and start rendering immediately before the view is completely processed. The web browser

Re: Any inerest in Zlib pre-compressed HTML generator responses?

Hi, To me it looks like this can live just fine outside Django core as a separate package since it doesn't look that it requires any changes to Django core itself. So for the community it doesn't need to be within Django core, you can already do it for all existing and future versions -

Any inerest in Zlib pre-compressed HTML generator responses?

Hi, I’ve been using zlib compression on my custom view responses on my site (https://www.futureclaw.com). I do this before I even cache, and I store the compressed responses in my Redis cache. This effectively increases my Redis cache size by about 10x. It also reduces response times from