Saving SSI files

[AliW]

We are starting to use SSI's within our Dreamweaver templates. Can anyone tell me if they need to be saved in a folder in the root i.e. SSI or if they can be saved in a sub folder i.e. shared/SSI/

Does it make a difference?

[Khalid Ali]

Your question have a better chance to get responses in the general forum.

[nkaisare]

Originally posted by AliW
if they can be saved in a sub folder i.e. shared/SSI/

Does it make a difference?
They can be saved anywhere.
<!--#include virtual="path-to-the-included-file" -->

[AliW]

Does it not load faster if it's in the root though?

[khaki]

hi Ali...

i doubt that it really matters much - if at all
(exactly how much faster do you expect it to get? :) ).

ultimately...
i think that it's easier to manage external files when they are saved in sub-folders.

but...
whatever makes you happier :)

;) k

[AliW]

Thanks for your help.

That's what I thought to be honest - just wanted to check that if I added them in sub folders I wouldn't slow the site down.

[nkaisare]

As long as they are on the same server, it doesn't matter. An external file (ie. on a different server) will take longer as it means http request to another server.

[nkaisare]

BTW, there are a few things that will slow the site:

1. Too many SSIs on a page - each SSI means a server request to read a different file. Limit number of SSIs just the way you limit number of images (well not quite, but you get the idea :))

2. Making server parse html file when there are no SSI in them. What I mean is that if you do not have an SSI in an html file, do not have it named .shtml. To parse an SSI, the server has to read the entier .shtml file. If your file contains no SSI, making server read that file is unnecessary.

[AliW]

Thanks.

We've not been naming the files with SSI's in them shtml though as we changed something on our server to read html files as shtml.

Would it be faster to have html and shtml files?