-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dossy Shiobara wrote:
| Server-side compression is perfume to cover up the stink of a poor | content representation format (HTML/XML). Of course, considering how | well-established this poor format has become, solving the real problem | correctly will likely never happen.
While the problem is certainly _exacerbated_ by inadequate site design, it is by no means caused by that entirely. Ya gotta pump bits to the user, and those bits can usually be compressed to a significant degree.
| Suggesting that "compression is the right solution" makes me wonder why | people aren't pressuring manufacturers of network-edge hardware (i.e., | Cisco) to design and implement transparent inter-router compression | standards to minimize the required bandwidth between peers. It's a | silly suggestion, and IMHO, just as silly as the application-level | compression thing.
Doesn't answer the problem of the end-points, namely, the client and the server.
| The pressure should be applied to content producers to ensure that their | images are optimized and cropped, that the HTML is clean and as much of | it is client-side cacheable, etc. Browsers and servers should support | things like If-Match: and If-Modified-Since: the ultimate compression is | to not transmit the data more than once, reducing payload to zero bytes.
Agreed. But when it's customizable, non-cacheable data, that doesn't help. The other extreme is making everything completely and "permanently" cacheable, which only serves to cause cache thrashing as objects get expired due to no more room.
Non-cacheable content may be a relatively small percentage of the traffic now (and I say may because I have no idea), but as more and more things become customized, it'll become more and more of an issue.
| -- Dossy
Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCI196XXdpNt6Ev7QRAkRxAKCey7+OioL/2Sk8a+ZCSqKa5J1tOwCfQcv0 TGAOIOkaVfuUm5ZDPL0ILdo= =Q64d -----END PGP SIGNATURE-----
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
