Javascript footprint and compression

vinsdeon — Fri, 11 Sep 2009 05:51:59 GMT

As per the documentation of webgrid, with client binding, the size of javascript footprint could be significantly reduced. And as i seen from another topic in this community, the code below could

<add key="ISNet.WebUI.ISRes_Compressed" value="true" />

reduce the data by enabling compression. But by checking YSLOW, i could see that the corresponding javascript and gzip format differ in size by a large and from firebug Net result i could see that total size is not altered at all. So i cleared cache, restarted the project and refreshed smartwebresources. No change at all. What i am doing wrong? Am using Webgrid 7.0 with SP1 installed. And what about the following lines

<add key="ISNet.WebUI.v3_0_5000.OptimizeCss" value="true" />
<add key="ISNet.WebUI.v3_0_5000.OptimizeCssName" value="true" />
<add key="ISNet.WebUI.v3_0_5000.GroupCssStyles" value="false" />

ClientBinding and Compression

danjransom@gmail.com — Wed, 19 Aug 2009 17:53:17 GMT

*I duplicated this post deliberately. The first post wouldn't open for me - error page.

I was looking at the client binding feature in the 2009 version of the grid to determine the bandwidth savings that this would produce for us. I found something very strange:

It loks like the client binding feature can increase the size of the data transmitted - rather than saving bandwidth. This is because the JSON data is sent uncompressed, while the older XML version of the data appears to be sent with with Gzip compression.

I tested this with the ClientBinding_BindingEvents.aspx sample page that comes with the grid. With server binding enabled, refreshing the grid on this page sends about 5.5 Kb (compressed down from 38.5 Kb) while client binding sends over 9 Kb.

Is there a way to turn on compression for the JSON data? I have II7 dynamic and static compression already enabled without effect.

Intersoft Community - compression

Javascript footprint and compression

ClientBinding and Compression