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
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.
Thanks. The SetImage method didn't work for me, but the CellElement version did. Note: the plus signs ( ) are missing from the for loop in the code block and this caused an infinate JavaScript loop.
I like the alert and I want to keep the alert. Is there a way to change the text of the alert?
Is there any way to change the text of this alert?
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.
The duplicate JavaScript entries were:
ISRes.axd?F/CoreValidator.js/305000701
ISRes.axd?F/corevalidator.js/305000701
and
ISRes.axd?F/CultureInfo.js/305000701
ISRes.axd?F/cultureinfo.js/305000701
Note that they have the same number attached!
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!
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.
2. It wasn't clear from the initial description, but combining IIS compression and ISRes_Commpressed produces no benefits in terms of the JavaScript. Although, IIS dynamic compression can shrink the size of the ASPX page.
3. There are a number of cases where the same JavaScript is downloaded twice. It looks like this is because the capitalization of the file names changed.
Is there any way to pre-load the JavaScript or somehow keep it (semi) perminantly cached on the client? Because of the way our application works we can't just set the cache expiration policy that way for the entire ASPX page.
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 tested this with the latest version of Safari (which is documented to support both kinds of compression) and looked at the Web Inspector tool for a page that has a grid, combo, web dialog box, and web imput. Between the JavaScript and the object definitions in HTML the page took up nearly 1.5 MB!! I compared with and without this setting and compared the 2008 version of the grid to 2009. Not only was there no improvement, but the footprint size actually went up.
I need to see a sample of how to implement this new compression feature.
What is the expected javascript footprint for a page that uses all four of these features: grid, combo, web dialog box, and web imput?
We purchased the latest version of the grid specifically because of this new compression feature and we need to have it work for us.
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...