Re: hitting the limits
- From: Jerry Stuckle <jstucklex@xxxxxxxxxxxxx>
- Date: Sat, 29 Apr 2006 22:28:52 -0400
windandwaves wrote:
Jerry Stuckle wrote:
windandwaves wrote:
Jerry Stuckle wrote:You can write perfectly good xml or html without obstart(). The two
....
Why even us it? I find very seldom do I need it. And it does add
overhead.
I use it on all my sites because in that way, I can perfectly indent
my code but take out the 100s or even 1000s of spaces/tabs.
For all my sites, I make a login and when the person is logged in
(i.e. me the administrator), the page is produced with spaces so
that I can analyse the code.
I like writing xhtml strict with real simple xhtml that is
compressed (i.e. without spaces) so that the actual pages are super
small. I do this to protest against the dreamweavers out there, who
create html that is often over 100kb and just pollutes the
superhighway with endless <td><img src="spacer.gif">etc......
HTMS
Nicolaas
have nothing to do with each other.
But compressing a page then expanding it just to make the code more
readable doesn't make sense. Just expand it in the file and serve it
statically. There's much less overhead.
What I do is for any user that is not logged-in, I compress the page getting rid of the 1000s of spaces and tabs. For the select few that log-in, I do not compress it so I can quickly spot errors in the code.
I think the only time I've really needed obstart() is when I wanted
to wrap phpinfo() in another page. In that case I needed to get the
output, parse it, getting rid of the extra tags, then print it.
I just like ditching all the html at once. Bang, 3Kb of perfectly clean (x)html. The css, javascript and images are bulkier, but these are often cached. Hmmm, you are probably right though, I would involved a LOT of changes :-)
And what happens if you have a problem with your compression?
I'm now beginning to see why your provider is suspecting your scripts are a problem.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@xxxxxxxxxxxxx
==================
.
- Follow-Ups:
- Re: hitting the limits
- From: windandwaves
- Re: hitting the limits
- References:
- hitting the limits
- From: windandwaves
- Re: hitting the limits
- From: Jerry Stuckle
- Re: hitting the limits
- From: windandwaves
- Re: hitting the limits
- From: Jerry Stuckle
- Re: hitting the limits
- From: windandwaves
- Re: hitting the limits
- From: Jerry Stuckle
- Re: hitting the limits
- From: windandwaves
- hitting the limits
- Prev by Date: Re: hitting the limits
- Next by Date: Re: to optimize a select join
- Previous by thread: Re: hitting the limits
- Next by thread: Re: hitting the limits
- Index(es):
Relevant Pages
|