Tommy Pham wrote:
-----Original Message-----
From: Peter Lind [mailto:peter.e.lind@xxxxxxxxx]
Sent: Sunday, December 12, 2010 5:27 AM
To: Lester Caine
Cc: php-general@xxxxxxxxxxxxx
Subject: Re: ORM doctrine
<snip>
The reason for 'caching' needs to be understood before it is applied in
order to avoid the black holes that random caching is causing nowadays
already. How often do you hear "wipe the xxx browser cache"? And I know
if I am changing theme elements in bitweaver or phpgedview then I HAVE
to wipe the cache to ensure that smarty rebuilds the relevant pages.
Which underlines my point: caching is not icing on the cake but should be
thought of sooner in the process, contrary to Tommys point.
If the app is well designed, then you still could implement it later w/o major rewrite.
It's only well designed if caching is considered from the start - thus,
as Peter says, caching is not the icing on the cake, but should, must,
be thought of in the initial design process - if it's not, then the app
isn't well designed.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
