next few weeks.
:-)
-Original Message-
From: Mal McKay [mailto:[EMAIL PROTECTED]]
Sent: 14 March 2001 17:12
To: Steve Brett
Cc: [EMAIL PROTECTED]
Subject: RE: [PHP-DB] File Optimisation
I wouldn't know about flushing the buffer.
Another approach would be changing to ADO. This being an intra
[mailto:[EMAIL PROTECTED]]
Sent: 14 March 2001 16:57
To: [EMAIL PROTECTED]
Subject: RE: [PHP-DB] File Optimisation
it does work.
i've tested it using ie5 and the network traffic is reduced dramatically.
not much of an imporvement on speed though
would have to test it some more - do i need
Steve,
look at the output buffering/filtering methods in PHP (ob_) In
particular, you can enable the gzip filter to automatically zip your html
server side, assuming your user's browsers support auto gzip deflation,
which the newer browsers seem to
"Steve Brett" <[EMAIL PROTECTED]> w
Sent: 14 March 2001 16:11
To: [EMAIL PROTECTED]
Subject: RE: [PHP-DB] File Optimisation
The first thing I would look at ( having had the same issue ) is whats
actually in the document. I managed to reduce the size of data delivered by
60% by 2 methods.
1. Ruthless use of css in table formattin
Hi Steve,
if your users have all JavaScript enabled, you could generate the HTML-Doc
clientside, using things like document.write or document.writeln.
Hope this helps.
Greetinx,
Mike
Michael Rudel
- Web-Development, Systemadministration -
_
The first thing I would look at ( having had the same issue ) is whats
actually in the document. I managed to reduce the size of data delivered by
60% by 2 methods.
1. Ruthless use of css in table formatting.
2. Creating javascript functions for even the smallest inline feature such
as mouseover
