RE: RE: Perl solutions for large web sites?

You've got a point.

A lot of this page is dynamic stuff which relies on CPU power. Trying to do a page like this with static pages would take a long, long time. I would bet that the code for this site is actually really small, but with a large database.

He could set up some scripts to generate stuff from templates every 10 minutes. This would give him the reduced overhead of not generating on the fly, but would give the illusion of dynamic generation, but only really work a few minutes out of every 10. That would be a good mid-grade solution, I think.

Comment on RE: RE: Perl solutions for large web sites?

Replies are listed 'Best First'.
RE: RE: RE: Perl solutions for large web sites? by Aighearach (Initiate) on May 24, 2000 at 10:39 UTC
You can set up a caching proxy server as the front end, and have it cache your dynamic as well as your static content. This does require setting correct headers. There are more details in the apache mod_perl guide, check out http://perl.apache.org/guide/ Also you can stack apache handlers so that all your HTML documents get sent through a ssi like process, that wraps the headers and menus around it. That is what I am doing for makeyourbanner.com, because I want to escape the mess that I made by implementing the whole thing with CGI.pm. CGI.pm is a WONDERFUL tool, but I'm not sure about the wisdom of writing large HTML with it; it's a mess, because you have to visualize both the HTML and the perl at the same time. With a wrapper, you get the same effect, only writing the menu once, but you don't have think about more than one language at a time. Very handy if different people are handling different parts of the site...	[reply]

Replies are listed 'Best First'.

RE: RE: RE: Perl solutions for large web sites?
by Aighearach (Initiate) on May 24, 2000 at 10:39 UTC

http://perl.apache.org/guide/

Also you can stack apache handlers so that all your HTML documents get sent through a ssi like process, that wraps the headers and menus around it. That is what I am doing for makeyourbanner.com, because I want to escape the mess that I made by implementing the whole thing with CGI.pm. CGI.pm is a WONDERFUL tool, but I'm not sure about the wisdom of writing large HTML with it; it's a mess, because you have to visualize both the HTML and the perl at the same time. With a wrapper, you get the same effect, only writing the menu once, but you don't have think about more than one language at a time. Very handy if different people are handling different parts of the site...

[reply]