[EMAIL PROTECTED] wrote: > >> On a development environment it could not be a good idea since it makes >> debugging a little harder (if you like to sniff the HTTP flow at least :). > > Okay...but how many people do this? I'm guessing very, very few. > Shouldn't they be the ones forced to turn it off? > > I just think that lots of people are going to overlook turning it > on.... The people who are advanced enough to do http "sniffing" will > have no problem turning it off. > > Perhaps it could be setup that when in debug mode it is by default > off, and when in production mode it turns on automatically by default.
I have to disagree with your opinion. It's definitely not a great idea while developing as you want everything as transparent as possible. On a production server though it's something that depends on deployment. Are you willing to sacrifice cpu for bandwidth? If you deploy behind apache what if you'd prefer it takes care of it for you? In my workings I've yet to find something that defaults to gzip on by default. Can you provide any examples where this is standard procedure? I think it should be handled like apache does, it's a feature that's there if you want it, but not on by default. Just my .02 Rick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
