iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Latest Development Blogs
Browse By Tag
Is there some way to decrease this footprint or to minimize the impact for slower connections?
Dan, are you running WebUI Studio 2009?
There are two ways you can reduce the footprint for slower connections:
<add key="ISNet.WebUI.ISRes_Compressed" value="true" />
With the simple line above, the scripts will be automatically compressed using gzip or deflate encoding depending on the browser capability (most browsers today accept both gzip and deflate encoding).With compression enabled, the overall footprint size for scripts can be reduced by 80%. This will dramatically improve the application speed especially in slower connections.
Hope this helps. Let me know if the solutions above worked for you.
I was glad to hear about the new compression feature as IIS compression is not an option for us. Based on your recomendation, we purchased the 2009 ASP.NET Suite.
My problem is:
1. I can find absolutely no documentation on this feature. In fact, we found very little documentation at all about the web.config options that are available and how they interact. For example, can this compression setting be used in conjunction with XMLCompression or the CSS options? Are these cumulative or competitive? What affect do they have on the CPU and memory requirements for the server or client system?
2. The "Deployment Manager" tool doesn't have an option for this new compression feature. In fact, this tool itself is also very poorly documented.
3. Putting the line you suggested into the most logical location in the web.config file did not result in any change in the overal footprint size.
I need to see a sample of how to implement this new compression feature.
We purchased the latest version of the grid specifically because of this new compression feature and we need to have it work for us.
Dan, thanks for your response.
Here are the answers to your questions:
A note regarding the compression level, the SmartWebResources compression feature used medium compression level to have a good balance between output and performance.
In most cases (and per my inspection on each compressed script), the average compression is at 75% level. That means, if the total size of uncompressed scripts is 1.5MB, then you can expect the total size after compression to be approximately 375 - 400 KB.
Please let me know how you find the results at your end.
Here is what we found using IE 8:
1. Setting the value of ISRes_Compressed to true or false didn't matter. If the line was in the web.config file then the compression was on.
Dan, thanks for sharing your results. It's great to see the compression worked at 72% level for you.
Several points for your questions:
The built-in cache setting sets the expiration to occur when the files are modified since last access (based on modified date of each resource).
Let me know if you have other questions. Thanks!
The development machine running this example has the older version installed, but the only files in the bin folder (these are not referenced rather they are physically located in the bin folder) are the 2009 versions. The CommonLibrary folder is not included and is not aliased. the web.config file has not reference to the older versions.
Note that they have the same number attached!
Thanks for following up on this duplicate issue.
We've found the issue which appears to be in WebInput, and has been resolved. The fix will be available in upcoming service pack.
Forgot your password | Sign up
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
Already a member? Sign in