RE: [PHP] stripping white space?
| From: | Maxim Maletsky | Date: | Tue, 10 Jul 2001 06:50:04 +0000 |
| Subject: | RE: [PHP] stripping white space? | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-57091@lists.php.net to get a copy of this message | ||
Bart,
a project we are working on will have:
1. HTTP compression, which is not 100% compatible, but catches most
of the browsers anyway.
2. Our own caching system: in two words: ob_*() to save the output
as a text file, mod_rewrite to check for file and throw the plain .txt files
if exist, PostgreSQL triggers to update (delete cached) .txt files.
3. Browser/Platform detection: there's no need to make
cross-platform heavy but compatible pages, just specific style sheets and
html tags for specific browser families.
4. clever HTML design, so there are less tags, tables etc, to have
files smaller. And *that* also includes less comments and double quotes on
integers. We do nothing with XML, so that is why I am so shocked why people
here discourage me that much.
-maxim maletsky
-----Original Message-----
From: Bart Veldhuizen [mailto:bart@blender.nl]
Sent: Tuesday, July 10, 2001 3:31 PM
To: php-general@lists.php.net
Subject: Re: [PHP] stripping white space?
Hi Brian,
> * Persuade someone at Zend to modify PHP so that a filter function can
> be specified which all output text is passed through - would have the
> same restrictions as the "header" function
You can already achieve this by using the built-in output buffering
function. Read http://www.zend.com/manual/function.ob-start.php
for more
information and a simple example on this.
Why not go for HTTP compression though? The gain would be much larger than
just stripping out the whitespace/comments and such..
Have fun,
Bart
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
For additional commands, e-mail: php-general-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net