Last modified: 2007-04-03 20:13:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T11488, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9488 - optimize js/css output
optimize js/css output
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://phpclasses.mkdata.net/browse/p...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-03 20:06 UTC by Carl Fürstenberg
Modified: 2007-04-03 20:13 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Carl Fürstenberg 2007-04-03 20:06:33 UTC
The question I have is: Would the code-size reduction by using something similar
to GzOutput, on mainly js/css, result in a net gain of performance/bandwidth
throughput? If so I propose to implement/use the package linked.
Comment 1 Rob Church 2007-04-03 20:08:41 UTC
We already use output compression, where supported by the browser and web server.
Comment 2 Carl Fürstenberg 2007-04-03 20:10:22 UTC
I know you have compression, I was thinking more to remove comments and
whitespaces and such things also.
Comment 3 Rob Church 2007-04-03 20:13:15 UTC
(See previous discussion on wikitech-l)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links