>
> So let me repeat that, as I think this is fundamental. A site *must* be
> able to perform withouth caching. Caching should be used as an extra
> improvement, not as a cover-up for bad design.
Not to turn this into a holy war or anything, but I think this statement is
simply wrong. There _is_ some truth to what you are saying. Before
willy-nilly adding caching you should always check to make sure there isn't
a code modification you can do to speed up the site. But, sometimes, no
matter what you do, a page will be slow for whatever reason.
Heck, sometimes I cache pages that _aren't_ slow. For example, if I have a
home page that takes 50-60ms to render, and if I can cache it to get it down
to 20-30 ms, why _not_ do it, especially if the page doesn't serve dynamic
content on a per-person request.
As for your comment that bugs are swept under the rug - I respectfully
disagree with you. I know that we work very hard to fix every bug that we
can. I also know that the 1.5.1 release will not only be a speed demon, but
should also be pretty darn bug free. No, it won't be 100% bug free. I have
yet to see a product that was 100% bug free, but with the community source
site coming, it will be easier to get bugs fixed and approved and out to the
public.
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
ICQ UIN : 3679482
"My ally is the Force, and a powerful ally it is." - Yoda
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
