Right now I wont say that the idea of SSI is bad its just that the usual
SSI implementations that I come accross are usually when I see them
going wrong. The most common example is of that of including content for
banners. I dont know whether it is a configuration goofup or something
else but I have noticed quite a few times the application aborting and
then the abort message turning up instead of the banner. If that person
was doing a system call I am assuming he would have read it some where
in a book or by perldoc - in any case it is well documented to trap
errors. In my opinion I would have a rather well informed user putting
HTML and other applications on my server than assume ignorance on their
part.
I have even seen users including HTML content by doing a "cat
<filename>" - bad practice but then I could always claim my users dont
know any better cant I.
Another thing isnt SSI supposed to be slow for almost everything other
than very rudimentary fucntions and that
Finally SSI can be almost as good a replacement for rudimentary CGI and
some templating work but I feel in the long run it is better to put a
proper script or a template mechanism in place rather than sticking to
SSI. Atleast I would rather make the effort to give a alternative
solution to SSI.
Mithun
