Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.8.2
-
Fix Version/s: 3.1
-
Component/s: Documentation, Bridge, Framework
-
Labels:None
-
Environment:Any
Description
We currently compress the resources served up the framework (e.g. icefaces-d2d.js) by default but not the DOM updates returned as Ajax responses. Since compression would only be optimal in certain situations, for example compressing a response that is past a certain threshold, the logic for doing this should be somewhat configurable.
Just as an example, we could provide a configuration parameter that sets the threshold for compression based on the number of bytes:
<context-param>
<param-name>com.icesoft.faces.compressUpdates</param-name>
<param-value>1024</param-value>
</context-param>
Setting the parameter to 0 would mean that compression is always done. Setting it to -1 could mean it's never done, and any other size would be the payload size threshold to apply compression.
Just as an example, we could provide a configuration parameter that sets the threshold for compression based on the number of bytes:
<context-param>
<param-name>com.icesoft.faces.compressUpdates</param-name>
<param-value>1024</param-value>
</context-param>
Setting the parameter to 0 would mean that compression is always done. Setting it to -1 could mean it's never done, and any other size would be the payload size threshold to apply compression.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking won't fix. The compression issue has been addressed via
ICE-8092.Basically, compression of resources is considered an application deployment time configuration and should be done via existing app. server or web server mechanisms. See http://wiki.icesoft.org/display/ICE/Resource+Compression for more information.