knl@xxxxxxxxxxx wrote:
Hi. I am currently looking into improving a system that (like many systems) generate static content at runtime. I have always been against generating static content at runtime and believe static content should be generated by a cronjob or manually at some idle time (if possible). This will provide real static content (no PHP at all) that doesn't need to be checked every time a request is made hence a huge performance benefit is achieved.
Does your needs really call for a publishing system at all? Back in the day, machines were slow and search engines didn't like much of the URL past the "?".. thus creative app design was needed to get around these issues, such as publishing systems and caching etc... Since it was stated you are "improving a system".. I thought this would be something to consider.
Today, it's a lot easier to create a punctual, scalable, and search engine friendly app that doesn't use a publishing system (nor caching). Anyway, my point is sometimes "improving" a system, can mean making it simpler. If publishing or caching is not needed, why complicate the matter?.. and btw, I found that Billy Hoffman article to be inaccurate in many of his assertions.
Cheers, Donovan -- D Brooke -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
