Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #6064
| From | "Peter H. Coffin" <hellsop@ninehells.com> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: flush() with gzip |
| Date | 2012-05-14 17:40 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnjr32fq.4ci.hellsop@nibelheim.ninehells.com> (permalink) |
| References | <4680629.1133.1336875252136.JavaMail.geo-discussion-forums@ynja13> |
On Sat, 12 May 2012 19:14:12 -0700 (PDT), Jason C wrote:
> I had read a couple of references (on Yahoo Developer, maybe?) to use
> flush() after the <body> tag to help speed up the delivery of a page.
> I'm not really having a speed issue at the moment, but figured that a
> gain of 500ms might help save a little server stress.
What problem are you trying to solve?
> The thing I'm not clear on, though, is whether this works with Gzip
> compression, or is using Gzip taking precedent over flush() and making
> flush() irrelevant?
gzip is certainly adding its own buffering to the mix, beyond what you
can control within PHP.
--
93. If I decide to hold a double execution of the hero and an underling
who failed or betrayed me, I will see to it that the hero is
scheduled to go first.
--Peter Anspach's list of things to do as an Evil Overlord
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
flush() with gzip Jason C <jwcarlton@gmail.com> - 2012-05-12 19:14 -0700
Re: flush() with gzip "Peter H. Coffin" <hellsop@ninehells.com> - 2012-05-14 17:40 -0500
Re: flush() with gzip Jason C <jwcarlton@gmail.com> - 2012-05-15 20:14 -0700
Re: flush() with gzip Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-05-15 21:01 -0700
Re: flush() with gzip Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-15 07:56 -0400
Re: flush() with gzip Jason C <jwcarlton@gmail.com> - 2012-05-15 20:17 -0700
csiph-web