'. '

ObfuscatePerLibrary

From APIDesign

Revision as of 12:42, 3 April 2013 by JaroslavTulach (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Bck2Brwsr supports static obfuscation mode when whole application is converted into a gigantic static JavaScript. This is not much different to what GWT does. However that looses the dynamic nature of Java and thus I'd like to achieve a state when we will do obfuscation per library - e.g. JAR file. Only some package (possibly individual classes) could be exported. By default everything would be hidden (obviously all private and package private methods).

I hope this could give us the benefits of deep obfuscation (most of the classes obfuscated) with ability to link individual libraries in an incremental fashion. Moreover we would not need enormous gigs of memory to compile modestly large applications.

Alternative Deployment

Browsers are optimized for consuming JavaScript (compressed by GZip). We tried to use ZIP, but it is not the most effective solution. That is why let's modify our maven archetype to generate alternative .js.gzip file for per JAR file. If the JavaScript file is found, let bck2brwsr use it. If not, let [bck2brwsr]] download and use the JAR file.

Design

TODO

Personal tools
buy