Re: Browser timing out.

Look at using server side compression, mod_Gzip or similar, PHP4.something also has compression handler built in.. When dealing with compressing raw HTML pages, very high compression levels can be reached.. Snippit from my mod_gzip+apache+php logs: ip.ip.ip.ip - - [21/Aug/2003:17:17:01 -0400] "GET / HTTP/1.1" 200 3450 "http://referrer" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Hotbar 4.3.1.0)" mod_gzip: DECHUNK:OK In:15234 Out:3450:78pct. ^^ 78% compression can cut data transfer down pretty quick! On Thu, 21 Aug 2003, J. Michael Roberts wrote: > unfortunately, it's not something that can be offline. What's actually > happening is the database is being queried for information that allows the > PHP script to find data files to be sent to the printer. The query really > isn't the problem, it's the sending of data when there is ALOT of data being > sent. Being that the actual data sent to the browser is minimal, both IE > and Netscape wait until there is something worth printing before it renders > the output. > > Basically, I need a way to force IE and Netscape to render the output so > that the user doesn't get a timeout notification. > > --JMR > > colbey@dreamwerx.net <mailto:colbey@dreamwerx.net> > wrote: > > > Perhaps change it to an offline report? I've done that in the past, it > > get's scheduled or backgrounded and the results are either emailed to the > > person, or generated report stored in the database for quick load later on > > (user gets email that report is ready for viewing).. > > > > > > > > > > On Thu, 21 Aug 2003, J. Michael Roberts wrote: > > > > > > Okay, I'm going mildly crazy now. > > > > I've got a huge query that runs and does all sorts of things...but the > > problem is that it's taking longer than the proxy server will allow to > > generate the HTML, thus the browser (IE) reports a timeout. > > > > I've successfully executed the entire script using Netscape, but Netscape > > appears to be a little more forgiving with it's buffer size than IE does. > > > > I've tried using a flush() call, but the output that is displayed to the > > user is fairly small in comparasion to all the stuff that's going on in the > > background. > > > > Is there a way to get IE to display the data it has received on the fly? If > > not, is there a way to force IE (and netscape) to use a smaller buffer size? > > I've thought about filling up the output buffer with some hidden garbage, > > but that would just be silly. > > > > Any thoughts would be greatly appreciated. > > > > --JMR > > > > > > > > > > > > > > > >