Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The bad part of 4.5.1 no one ever knewThe bad part of 4.5.1 no one ever knew
Previous
 
Next
New Post
5/15/2007 8:10 AM
 
Raldo Loots

Joined: 9/29/2005
Posts: 36

I see comments about enabling compression and on the other hand about compression breaking the Javascript.

Is the conclusion then; 1. Do not enable compression if you use AJAX, 2. Enable compression if you are not using AJAX???
 
New Post
5/15/2007 9:31 AM
 
Brandon Haynes Haynes


brandonhaynes.org
Joined: 2/6/2006
Posts: 1172
The discrepency between your payload sizes and the original poster's is almost certainly due to the latter site being run in debug mode instead of release mode. In this scenearo, I know that the ajax payload is significantly higher (due to more verbose debugging information, extra whitespace, etc). To make matters worse, a client of a site run in debug mode will be forced to download the ajax payload on EVERY request, rather than caching it on the first request. An extra 23k on the first request -- and never again thereafter -- is no big deal at all.

Check your debug switch!

Brandon
Brandon Haynes
BrandonHaynes.org
 
New Post
5/15/2007 10:19 AM
 
John Mitchell


www.snapsis.com
Joined: 4/18/2003
Posts: 3987

BrandonHaynes says:
 An extra 23k on the first request -- and never again thereafter -- is no big deal at all.

Hi Brandon,
I disagree that it is no big deal.  If it is needed for some functionality then that payload may well be worth the cost, but if it is just there because it is no big deal then it is wasted bandwidth and time waiting for every first time visitor to our sites.  This is the same argument that is used for the Solpart  Menu JS, and it is 67K, so all total it is up to 100K. When does it become a big deal?

DotNetNuke Modules from Snapsis.com
 
New Post
5/15/2007 10:22 AM
 
John Mitchell


www.snapsis.com
Joined: 4/18/2003
Posts: 3987

raldo wrote

I see comments about enabling compression and on the other hand about compression breaking the Javascript.

Is the conclusion then; 1. Do not enable compression if you use AJAX, 2. Enable compression if you are not using AJAX???

You should be able to have both.  If compression is interferring then it should be configured to exclude Ajax requests.

DotNetNuke Modules from Snapsis.com
 
New Post
5/15/2007 4:30 PM
 
Mitchel Sellers


Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

www.mitchelsellers.com
Joined: 1/24/2007
Posts: 7846

I have been using compression with AJAX and not having any problems! 

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
 Page 2 of 4
Previous1234Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...The bad part of 4.5.1 no one ever knewThe bad part of 4.5.1 no one ever knew


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