To SSI a page or not SSI a page - That is the Question!!!

[WP1]

Hi,

I am looking for the opinion of the SitePoint Community as a way to get some knowledge about SSI's.

QUESTIONS

1. Is it wise to make a total "Virtual" (for lack of another word) page where the entire page is made up of SSI's???

2. If for some reason you do not feel a total page of SSI's is wise, what items do you feel should be coded on every page and not SSIed, so to speak???

WP

[James]

I think that the layout/design should always use SSIs wherever possible...it means that to update the design only one page need change.
Also for PHP sites I always put the database connection information in an SSI file..
Hope that helps!

[Vincent Puglia]

Hi WP,

From my point of view, SSI isn't client-side, but since I'm not certain where this should go I'll leave it here until someone says otherwise.

Since SSI requires server time, I would limit the SSI to code that would best be served by a SSI script, such as session and access information. Otherwise, you may notice slower response time.

So, what sort of information do you intend to relegate to the SSI?

James' statement about one-page updates is true; however, the same may be said for js and css files (both of which are loaded and executed by the surfer's computer and, therefore, client-side processing).

Vinny

[jonese]

This is a server side question. please see the post in that forum.