28 Jun 2007
14 Jul 2009
Link to this post
Thanks for the answer we did manage to prove the case using the Script Manager, but it's interesting that you mentioned using the RadScriptManager.
One question I have about this is as follows:
With script combining I'm assuming that Asp.net is putting together the required scripts into one batch, which is then cached on the client side. What I'm failing to see is how combining scripts in this way is beneficial across the site as a hole, especially when used in Master pages and situations like Sitefinity. Fewer requests yes, but consider the following:
1. The home page of our Sitefinity site uses Home.Master which combines X scripts into one
2. The about us page uses TwoColumn.Master, but also includes the use of a different control that might require an extra script resource.
In this scenario, the home page would have combined and loaded say 5 script files into one, but the About Us page needed only one extra script resource. What this effectively means is that the browser would have to reload the entire combined script file again, because in effect it's definition has now changed, or the cached version no longer applies. So Asp.net would have to re-combine all these files again into one bigger file and download a new script file to the browser.
Is my understanding of this correct?