On 9/19/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
too much work - and there are some pretty massive sites out there running on django or Rails using dynamic content - the bottleneck is not translating text. It is serving media - django advocates serving media from a separate server from the filesystem and not the database.
Dynamic sites are hard to scale for large/massive number of users as compared to static sites. The design idea should always be to push as much stuff into static content (using pregeneration/preprocessing as needed), keeping only things such as user preferences dynamic. Media should never be served from DB if you are serious about page-load times on the client and performance/scaling of the webserver.
obvious - but the less dynamic content, the more work for the programmer and there is no fun in being a programmer if you have to work
It is less work for the programmer in the long run. It is better to pregenerate pages and serve them rather than being called up in the night when users decide to swarm to your website. -- Vinayak -- http://mm.glug-bom.org/mailman/listinfo/linuxers
