March 13, 2010
FindBugz Community Review. I am very fond of FindBugz (indeed it has found its way into the QA process of most projects I work on....). When visiting the site to check Eclispe 3.5.2 compatibility I found they were working on a new tool.
Indeed a very interesting tool.
Looks li...
More »
March 12, 2010
Oracle Java and PRINCE2. Looking already at SOA and ITIL, I started reading up on other project lifecycle standards popular in the United Kingdom. PRINCE2 (PRojects In Controlled Environments) methodology naturally was the one that caught my attention. I'm not going t...
More »
March/2010
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| | 1 |
2 |
3 |
4 |
5 | 6 | | 7 |
8 |
9 |
10 |
11 |
12 |
13 |
| 14 |
15 | 16 | 17 | 18 | 19 | 20 | | 21 | 22 | 23 | 24 | 25 | 26 | 27 | | 28 | 29 | 30 | 31 | | | |
|
 |
Automatic compression of jsf.js
Just a quick note that we've now added automatic compression of the jsf.js file served by JSF 2. The file size of jsf.js, 71k uncompressed, comes to about 16k compressed (there are a lot of comments in there).
There is no user action required to make this happen: If the Project stage is Development, the file is served uncompressed (for ease in debugging with something like Firebug), but if the Project stage is anything else, then the file is compressed (and essentially unreadable, since besides stripping all comments, variable names are stripped, as well as all line breaks).
Date: July, 03 2009
Url: http://weblogs.java.net/blog/driscoll/archive/2009/07/automatic_compr.html
Others News
Leave a Reply
Related
- Automatic data compression ABSTRACT. The “information explosion” noted in recent years makes it essential that storage requirements for all information be kept to a minimum.
|
