Nov 16, 2009, 5:02 AM
Coolite support for Content Delivery Networks
I hope I am posing a new challenge for the Coolite team.
As anyone would expect, ASP.NET web applications get bigger & slower as you use more built in services. With each new HttpModule & HttpHandler added to web.config, with each new assembly added to bin, and with each new such things, ASP.NET apps put to much of a load on an average server.
Now, I typically use DotNetNuke (DNN) for solution development. People who have used it would agree that it is bulky (maybe too bulky). For keeping the web-server optimized for dynamic content delivery, I recently purchased a subscription for Amazon AWS service. As people here might know, AWS is a content delivery network for offloading static content from your servers.
Now, Coolite enabled pages deliver too much of static content to the page (images, stylesheets, javascripts and what not). I was wondering if Coolite team can work in the direction of integration with Content Delivery Networks which is not possible right now. This would provide a significant boost to Coolite/ExtJs based applications.
I also have a suggestion which might help in implementing this. I believe, that such integration should NOT require any changes to any other part of the Coolite framework, except the ScriptManager class.
You can introduce a new property in that class e.g. ContentbasePath
I might use that property like:
1) Change the urls generated by ScriptManager if this property is set, to be relative to this path.
2) Provide a folder containing static content that we should upload as it is to the root path of this property.
That should provide a significant boost to the application performance. Any thoughts from the Coolite team!!!
As anyone would expect, ASP.NET web applications get bigger & slower as you use more built in services. With each new HttpModule & HttpHandler added to web.config, with each new assembly added to bin, and with each new such things, ASP.NET apps put to much of a load on an average server.
Now, I typically use DotNetNuke (DNN) for solution development. People who have used it would agree that it is bulky (maybe too bulky). For keeping the web-server optimized for dynamic content delivery, I recently purchased a subscription for Amazon AWS service. As people here might know, AWS is a content delivery network for offloading static content from your servers.
Now, Coolite enabled pages deliver too much of static content to the page (images, stylesheets, javascripts and what not). I was wondering if Coolite team can work in the direction of integration with Content Delivery Networks which is not possible right now. This would provide a significant boost to Coolite/ExtJs based applications.
I also have a suggestion which might help in implementing this. I believe, that such integration should NOT require any changes to any other part of the Coolite framework, except the ScriptManager class.
You can introduce a new property in that class e.g. ContentbasePath
I might use that property like:
<ext:ScriptManager runat="server" ContentBasePath="http://static.mydomain.com" />
Then, all that the Coolite team needs to do are 2 things:1) Change the urls generated by ScriptManager if this property is set, to be relative to this path.
2) Provide a folder containing static content that we should upload as it is to the root path of this property.
That should provide a significant boost to the application performance. Any thoughts from the Coolite team!!!