I don't think this should be tapestry's job. There are a tonne of
filters already out there ( i think httpcomponents now has one too ),
and native support from most app servers. Don't waste your time, or
confuse the compression feature already done by other layers.
Howard M. Lewis Ship (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TAP5-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAP5-70:
----------------------------------------
Assignee: Howard M. Lewis Ship
Tapestry should automatically compress content sent to the client, if the
client supports it
--------------------------------------------------------------------------------------------
Key: TAP5-70
URL: https://issues.apache.org/jira/browse/TAP5-70
Project: Tapestry 5
Issue Type: New Feature
Affects Versions: 5.0.15
Reporter: Howard M. Lewis Ship
Assignee: Howard M. Lewis Ship
Most browsers will accept gzip compression of the text stream. Tapestry should
identify which content types may be compressed, and (perhaps) minimum byte
counts to trigger compression. Thus text/html and text/javascript streams
might be compressed, but jpeg and png (which are already compressed) pass
through unchanged.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
