Wondering if anyone is using HTML compression to reduce the size of their pages and increase load time. Would love to discuss how to go about doing this. I had it setup in V6 but since we moved to V7 it has become more challanging...
- Murtaza
Hi Murtaza,
I've not heard of any customer (on V7) that has implemented custom html compression. The reason for this is that there are other strategies available in V7 to improve page loading times (that from a certain perspective provide "compression"): the DefaultObject Cache available in DPM/DSM, and an extension of this caching mechanism known as High Performance Delivery (HPD). The fragments of HTML generated from JSP/XSL/CSS are "pre-rendered" and delivered to the java heap of the Application Server. Each fragment (depending on the component it represents) is associated with a TTL value that auto-purges that object's html (or manually purged from the ICE menu on V7 Preview).
As an extention of the DefaultObject cache in DPM, HPD takes this quite a bit further and implements a site-wide, highly configurable caching strategy that improves dramatically page loading times for both dynamic content regions and non-dynamic regions.
You could still implement some kind of compression on the web servers BUT this would defeat the purpose of the caching mechanism that is out-of-the box.
What I have seen customers do is use mod_deflate on the static file docroots of http server to improve loading times of statics.
However with a properly tuned instance of DPM/DSM you can acheive very fast page load times without having to figure out how to encode compression techniques in the generated html.
Details of how to implement this are in the DPM/DSM Guides
Also here's the link to HPD documentation. This requires a seperate license however. You can get excellent load times with ootb DPM caching but HPD provides a more comprehensive solution.
One other thought. There exists an extension point in the default caching and rendering mechanism
Starting on page 102 of the DPM/DSM Development Guide, you will see an extension point for the implementation of a custom rendering and caching strategy. What you'll need to do is implement ICacheableObject in your extension code that uses the kind of compression you want to use. This would only apply to default or custom components however. For any other areas of the page you'd want to look at HPD or implement one of the many compression techniques on the http server.
Setting up gzip compression by using a web server in front of your servers is possible if you have compatible Browser for both VCM and Delivery sites. But setting it up correctly will require some expertise.
Best Regards
Qutubuddin SaifuddinSenior Consultant | America Services Organization
Phone:
(732) 354 4423
Mobile:
(732) 397 7951
Website:
www.opentext.com
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]Sent: Friday, March 30, 2012 4:00 PMTo: eLink RecipientSubject: HTML Compression possible?
HTML Compression possible?
Posted bymftohfa@peoples.com (F Tohfafarosh, Murtaza) On 03-30-2012 15:56
[To post a comment, use the normal reply function]
Forum:
Discussion Group - Web Experience Management
Content Server:
Knowledge Center
