Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Modern standards - bringing DotNetNuke up to them?Modern standards - bringing DotNetNuke up to them?
Previous
 
Next
New Post
6/9/2011 1:59 PM
 
Sebastian Leupold wrote:
as long as css and script files depend on modules used on certain pages only, combination does not really make sense (or you result in page specific larger downloads)

 If it was done properly, it would be loaded and cached per page.  Obviously you wouldn't want everything loaded in one file for every page as that would defeat the entire purpose.  

It's also just as important that module developers and skin developers take into consideration what is being loaded and how.  


Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
8/24/2011 5:19 AM
 
Isn't that exactly what Content Delivery Engine is for? Snapsis PageBlaster combines and caches all JS/CSS per page and can completely change anything on individual pages using regex (spoof emails, filter obscenity etc). It can also granulary cache pages which are static and can benefit greatly from caching. Also can create different cache based on user, role, browser or any other variable too. Look what I accomplished with PB after 30 minutes and I sure am not done, it can go all the way up to 100. http://www.xeev.eu/files/img/YSlow.png
 
New Post
8/24/2011 8:11 AM
 
PageBlaster does solve several of these issues, but does have a learning curve and extensive testing on more complex sites. That said, I've used it for what Xeev noted and it can also be used to create your own CDN with the use of S3 and CloudFront.

A CDN for all the common DNN scripts is a good idea, but it would need to be configurable at the host/admin level for sites that are on an intranet.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Modern standards - bringing DotNetNuke up to them?Modern standards - bringing DotNetNuke up to them?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out