On Wed, 2004-02-11 at 13:09, Jamie Heilman wrote: > Lennart Regebro wrote: > > OK, you get the problem that images may not load even if the main page does, > > but is that really worse for the end user than not getting anything? > > As I've been saying, if you do that, they will reload repeatedly > making the problem worse. If the images are fluf, and the user knows > they are fluf, then *maybe* they won't reload, and your pages will > simply appear ugly. But then you have to ask yourself, why am I > sending fluf images that degrades the overall user experience of my > application? Clearly there's more optimization that could be done to > your application.
Without knowing the app I'd probably say there are many ways that it can be made more efficient. For instance are your image urls being generated using Zope's acquisition? If so, don't do that. Another alternative is to move the static/fluf images out of zope and just let apache serve them. That's just small thing that you can do to reduce the load on zope. Things like squid, zeo, better hardware, re-analyze long running routines, etc are all possible without having to do the other gymnastics that have been discussed. -- Edward Muller - http://www.interlix.com - "Open Source Specialists" Dedicated Zope Hosting - Web Hosting - Open Source Consulting Network & PC Service & Support - Custom Programming Phone: 417-862-0573 - Cell: 417-844-2435 - Fax: 417-862-0572 Jabber: [EMAIL PROTECTED] - AIM: edwardam453 - ICQ: 287033 _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
