| Version 1 (modified by , 16 years ago) ( diff ) |
|---|
Proposal number : ? Proposal title : GZIP content compression filter to reduce network traffic
| Date | 2008/07/21 |
| Contact(s) | Simon Pigot |
| Last edited | Timestamp |
| Status | draft, being discussed, complete |
| Assigned to release | 2.3.0 |
| Resources | Test implementation is complete |
Overview
Compression reduces the size of the HTTP response and has been implemented since HTTP/1.1. This can speed up the time it takes for pages with lots of content to refresh and draw. Most developers don't realize this because they usually test using localhost. GeoNetwork makes a lot of requests and sends many responses - these will only grow as both the metadata standards and the content they contain grow richer and the user interface becomes more complex (read more JavaScript). As an example, a large iso19139 metadata record with a few sizeable select/pulldown lists took half the time it used to take to render when the compression filter was added.
A GZIP compression filter has been written for general use by the people at jspbook.com - Two servlet filters every web app should have - this filter has been adapted for use in GeoNetwork and a bug that caused trouble for Exploder has been fixed.
Proposal Type
- Type: Servlet configuration, configuration change
- App: GeoNetwork and Intermap
- Module: servlet configuration (web.xml files)
Links
Voting History
- Not voted on yet.
Motivations
The current configuration is .... A change to ....
Proposal
An in depth proposal can be found here : link ...
Backwards Compatibility Issues
Risks
Participants
- List of participants and role (if necessary) in current GIP
