PHP includes vs .shtml SSI's

[JackM]

Is one easier on the server load than the other?

I have a friend with a large site (hundreds of pages) that wants to
convert from a left hand menu area using Dreamweaver's templates that
require every page to be updated and uploaded when a change is made.

She has a few pages (about 12) currently online that are shtml pages
calling includes. She decided she'd like to convert all her pages so
they can by generated dynamically to make updating easier when changes
are made.

But I'm trying to see what the consensus is on server load doing that
versus doing PHP includes.

Thoughts?

[2metre]

Re: PHP includes vs .shtml SSI's

JackM wrote:[color=blue]
> Is one easier on the server load than the other?
>
> I have a friend with a large site (hundreds of pages) that wants to
> convert from a left hand menu area using Dreamweaver's templates that
> require every page to be updated and uploaded when a change is made.
>
> She has a few pages (about 12) currently online that are shtml pages
> calling includes. She decided she'd like to convert all her pages so
> they can by generated dynamically to make updating easier when changes
> are made.
>
> But I'm trying to see what the consensus is on server load doing that
> versus doing PHP includes.
>
> Thoughts?[/color]
If server load is very important, write a script that creates static
pages whenever a change is made.