On Friday, 10 December 2010, Tommy Pham <tommyhp2@xxxxxxxxx> wrote: * snup * > The way I see it is this: > > 1) Thorough understanding of the problem: needs of the client/company, > programming language in use, etc. > 2) Thorough understanding of the objective of the application: answer the > needs, capable of possible future growth/expandability, etc. > 3) Well thought out application design to resolve the above 2: Âframework, > mixed, or no framework. > > Thus, IMHO, caching is needed when one fails to fully meet the above 3 such > as when the user clicks on any link in the browser, it should take no more > than 3 seconds for the browser's status to be 'Done', provided that the user > isn't on some 56k modem connection ;). Always use a cache. Not using a cache means you've misunderstood some fundamental points. Regards Peter -- <hype> WWW: plphp.dk / plind.dk LinkedIn: plind BeWelcome/Couchsurfing: Fake51 Twitter: kafe15 </hype> -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
