I heard that there is a way to reduce the file sizes by using server side includes. how do you do this??
The following link is the post where I got this idea from:
The following link is the post where I got this idea from:
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SSI 1
- Thread starter kris29
- Start date
-
1
- #2
The idea is if you have any repetitive content you can cut down on file size and make your site more manageable by including the same file in multiple html files. The first thing that comes to mind are headers and footers. Of course it only helps if you have repetitive content.
Furthermore, I'm sure that his include files add up to 25k or more but thats only a few files as opposed to all of his html files.
Furthermore, I'm sure that his include files add up to 25k or more but thats only a few files as opposed to all of his html files.
missbarbell
Programmer
Rather than using SSI, have a look at template toolkit ( which handles some very complex templating one aspect of which is includes.
I currently have one site that uses a layout template which then includes 4 standard files (eg navigation, copyright) and 1 which is created dynamically from a database, which means I need only change one of the standard files for the change to be replicated thoughout the site. It also allows me to provide complex perl functionality to the individual files too.
The danger in using SSI is that you could potentially run dangerous code if it's anything more than a basic include of a flat HTML file.
HTH,
Barbie. Leader of Birmingham Perl Mongers
I currently have one site that uses a layout template which then includes 4 standard files (eg navigation, copyright) and 1 which is created dynamically from a database, which means I need only change one of the standard files for the change to be replicated thoughout the site. It also allows me to provide complex perl functionality to the individual files too.
The danger in using SSI is that you could potentially run dangerous code if it's anything more than a basic include of a flat HTML file.
HTH,
Barbie. Leader of Birmingham Perl Mongers
- Status