One idea for the JavaScript issues:
Before applying the compression replace all instances of <script> ... </script> with $script[x].
Afterwards run a special compression on the script-snippets (which should just ignore <!-- and -->, or maybe strip them but not the text within), then run the compression on the template (as there are no <!-- or // within JavaScripts now there should be no problems) and finally re-substitue the $script[x] with the script(s).

is it really so nessary with how vB3 is done?

You can get information here:

http://leknor.com/code/gziped.php

Simply enable it on your forum then enter your forum's url and you can see what benefit you're getting ;)

faranth,
yes, it does make a difference ... especially in the long run.
Less bytes = Less bandwidth / faster rendering (client side) / also, makes it harder to read source code (client side)

It's similar to putting entire source code (client side) in one line.
I like KirbyDE's idea - about doing the compression before hand.:up:

cirisme,
two different end results ... not the same thing

i dont belive its so nessary anymore, with alot of the files stored externally, and with the option to store the CSS externaly. i really dont think its going to improve it as much as it used to

all you have to do is look at the source code here and you will see a lot of




S P A C E
It's really a personal choice. However, as a web professional, I make sure my customers/friends get maximum results for their money.

Wouldn't the parsed templates need to be deleted before the hack will work? I guess this hack will require running a query on the MySQL database to install/uninstall it.

I used the vb2 version and it worked straight up for me. I have been using it for about a two weeks now with no problems. Then again im running a ported version of the vb2 microstats hack that i brought over a while back.