Newsgroups: php.general,php.internals
Path: news.php.net
Xref: news.php.net php.general:325690 php.internals:95465
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.175 as permitted sender)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CACMzB5cjhfs0s88ohW=Rq4DA2-2dv1-EKGt7ZWnSLT8Sb0OvKw@mail.gmail.com>
Date: Sat, 27 Aug 2016 15:00:53 -0400
Cc: Ashley Sheridan <ash@ashleysheridan.co.uk>, php-general@lists.php.net,
 internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <33E6F0A8-A14B-4590-A18C-FF6D6E029D0A@gmail.com>
References: <CACMzB5ccYey3m2h_eWzk+okDXy0ANWXD4M-Yv0JfJu2i=FMWnA@mail.gmail.com> <5E615A59-AC2B-455F-9438-D295419F3767@ashleysheridan.co.uk> <CACMzB5cjhfs0s88ohW=Rq4DA2-2dv1-EKGt7ZWnSLT8Sb0OvKw@mail.gmail.com>
To: Rene Veerman <rene.veerman.netherlands@gmail.com>
Subject: Re: [PHP] feature request : gzip caching
From: josh.kehn@gmail.com (Joshua Kehn)

Why is PHP handling static file serving? This is squarely outside of it's do=
main. Have nginx or something upstream handle gzipping content.=20

--jk

> On Aug 27, 2016, at 1:22 PM, Rene Veerman <rene.veerman.netherlands@gmail.=
com> wrote:
>=20
> 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...
>=20
> On Sat, Aug 27, 2016 at 7:19 PM, Ashley Sheridan <ash@ashleysheridan.co.uk=
>
> wrote:
>=20
>>=20
>>=20
>> On 27 August 2016 17:52:48 BST, Rene Veerman <rene.veerman.netherlands@
>> gmail.com> wrote:
>>> Hi..
>>>=20
>>> First off, i love PHP. Many thanks for keeping it free too.
>>>=20
>>> 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))..
>>=20
>> Are you building the js each time it's requested? Have you thought about
>> building it as a deployment step for production?
>>=20
>>>=20
>>> 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?
>>=20
>>> Could you pretty please add this to the core of PHP? Shouldn't be that
>>> hard
>>> for the internals team right?..
>>>=20
>>> Many thanks in advance for even considering to do this..
>>>=20
>>> with regards,
>>> Rene Veerman,
>>> CEO + CTO of seductiveapps.com
>>=20
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>=20