Implement 'use uncompressed resources' like in PFE
See original GitHub issueThe
<context-param>
<param-name>org.primefaces.extensions.DELIVER_UNCOMPRESSED_RESOURCES</param-name>
<param-value>true</param-value>
</context-param>
Can be very useful for people trying to find/fix/override things in the JS without the need to fully download the source and build a version with uncompressed resources. The amount of data in the jar should not be an issue, it is not that much). It could even be deduced or always active if the app is running in JSF Development Mode.
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Identifying Uncompressed Resources in your Web App
In this tip, I'll teach you how to quickly check if all of your resources are properly compressed.
Read more >IBM FlashSystem Best Practices and Performance Guidelines
Implementing the IBM FlashSystem with IBM Spectrum Virtualize V8.4, SG24-8465 ... to use and enable rapid deployment without additional resources.
Read more >The Lou Mass Storage System - HECC Knowledge Base
Lou uses a parallel Data Migration Facility (DMF) system to provide high speed and bandwidth for data transfers between Lou's disks and tapes....
Read more >Lossy and Lossless Compression Techniques to Improve the ...
Main memory is a critical resource in modern computer systems and is in ... parallelized implementation of the more advanced Squeeze (SZ) compression....
Read more >AVR: Reducing Memory Traffic with Approximate Value ...
architectures that use memory compression are graphics processing units (GPUs) [1]. ... a prefetcher (PFE) selects a number of decompressed cachelines,.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
we discussed it several times in the past and we decided to not do it as it blows up the jar. (me was the +1 😉) if you need to debug, you can still build PF by source as it will only be compressed with the release mvn profile.
not sure if i understand you but currently we have jar with compressed and aggregated resources only i don’t compare to the jar we build yesterday, today we the aggregation source files
if we would build the jar now from source, with both compressed+aggregated and uncompressed+aggregated, the jar will grow around 1-1,5mb compared to trunk now