eh no, i'm a big fan of caching output in js / json cache files :) but those still need to get gzipped... not just my main JS file, also my photoalbum contents -> another 1Mb of JSON content... On Sat, Aug 27, 2016 at 7:19 PM, Ashley Sheridan <ash@xxxxxxxxxxxxxxxxxxxx> wrote: > > > On 27 August 2016 17:52:48 BST, Rene Veerman <rene.veerman.netherlands@ > gmail.com> wrote: > >Hi.. > > > >First off, i love PHP. Many thanks for keeping it free too. > > > >However, i've noticed that gzipping the 1Mb of javascript that my > >seductiveapps.com needs, takes a relatively long time (measured over a > >total page load time which i'd like to bring down from it's current 10 > >seconds, about a second or even more is spent gzipping (by a core i5 > >machine)).. > > Are you building the js each time it's requested? Have you thought about > building it as a deployment step for production? > > > > >At one time, i spent time building PHP code that cached the > >already-gzipped > >content and outputted that with just readfile().. But i never got it to > >work a second time, unfortunately.. > > > Why don't you want the web server to handle the gzip side of things? It > would make more sense surely? > > >Could you pretty please add this to the core of PHP? Shouldn't be that > >hard > >for the internals team right?.. > > > >Many thanks in advance for even considering to do this.. > > > >with regards, > > Rene Veerman, > > CEO + CTO of seductiveapps.com > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. >
