Topic: SHTML

Im doing some pages in SHTML, so i can use SSI for menu's etc.

Is this bad to do these days? Or is it normal practice.


Technically it will slow my pages down a little, but surely it shouldnt be much...

Any thoughts?


Thanks

There is not much point using shtml, given there are better and more complete server side languages, that may fit your needs in a later future. Iwouldn't call it bad practice, just pointless

__________________________________
Something else

Sexy Demoness cel

Ahh ok, i was just using it for simple menu's so you only had to change one file to add ot the menu.

The alternative i guess is to use php for the task, i was along the line of thinking that perhaps .shtml was more friendly to search engines than .php .

The only thing i want to do is insert a menu file in there and nothing else. I guess it still is a server side languange, maybe google etc still treat them as dynamic pages?

Ive been testing it out a bit, and even on simple pages there can be a noticable slowdown.

Its like it gets to a point in the page then stops then goes again, whereas this doesnt happen in a completely static html file. I didnt think it would be that noticeable - having said that it doesnt happen everytime, sometimes its just as fast sometimes its slower.

php and shtml both in the end deliver 'real' html to the browser - neither is more search engine friendly or unfriendly than the other, or html.

Yeh i see your point..

Do you know if shtml would run slower than php?

I guess i can see how it goes and change if it needs it.

You think that php etc are just as friendly to search engines as php these days?

quote:

---

H][RO said:

m doing some pages in SHTML, so i can use SSI for menu's etc.

---

If you are using apache, you can use the XBitHack. Set the execute bit for the pages that you want the SSI. httpd.apache.org/ssi config