iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
*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.
Hi Dan, thanks for pointing out about JSON compression.
Actually, this issue is related to the setting in IIS 7 compression, not WebGrid. By default, all text content, which includes xml in this case, will be compressed in both dynamic and static compresion. But, this is not the case for JSON. Our live server also doesn't enable compression for JSON yet.
To enable compression on JSON, simply add "application/json" to the dynamicTypes of your IIS 7. When the setting is added, the JSON response should be compressed as well. Please click here to learn more about IIS 7 httpCompression. You may have to restart your server to get the new setting applied.
Hope this helps.
Dan, the client binding should give 80% less footprint when compared apple-to-apple (both uncompressed).
Yes, the JSON data should be compressed as well when you turned on IIS dynamic compression. A quick question, did you test our sample from the live sample/C# samples installed in your development machine? Please note that these samples are running from WebDevServer (file system mode), not IIS 7.
Let me know if you still unable to get the compression works in IIS 7 mode with compression enabled.
Yes, I used IIS 7. Yes, I have both dynamic and static compression enabled.
As I stated, you can see this behavior in your own sample pages.
Steps to reproduce:
1. Open up this page: Client Binding Sample
2. Start up an http inspector such as HttpWatch or Fiddler
3. Press the refresh button in the grid.
You'll see the JSON data is not compressed. If you take the same page and remove the "ClientBinding" setting the data sent is XML and it is compressed, actually to a smaller size!
That makes sense. Can I add a feature request?
We don't necessarily want to turn on dynamic compression because of the added CPU load. Can we get an option to have the datastream compressed via the Instersoft controls rather than setting this system-wide in IIS? This could also help when running on IIS 6.
Dan, that's a nice feedback. Thank you.
I've added your feature request to priority list and targetting it for the R2 milestone.
Let me know if you have other questions, or feedback.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname
Creating your account...