I've been going with the invisible data mathod right now and it doesn't seem
too bad. What happens on the page is not much to look at and it only
returns maybe 1K while the script is running. However, what's happening in
the background is a huge-ass transfer of data.
To the user, all that's happe
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] "G
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
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,
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,