Maverick — Fri, 17 Dec 1999 18:37:00 +0000

I just did a search for "rename" at download.com and the very first return was a little utility called NameWiz. It's available from http://softbytelabs.com and should also be listed on most of the major shareware sites. For batch filename editing like converting .htm to .shtml it works like a charm.

Fri, 17 Dec 1999 15:22:00 +0000

may i ask what batch renaming program you are using and where i can find it??!!

------------------
This Site is For Webmasters Only!!

webmaster@doubleok.com

Maverick — Fri, 17 Dec 1999 03:57:00 +0000

I never even considered the search engine aspect of things. I was only concerned about bogging down the server by forcing it to parse those pages rather than just loading them blindly. And yes, I was planning to make .htm extensions as SSI parsed. Editing the pages themselves to adapt the .shtml in place of .htm is simple enough, but now I've got to change all the file names by hand I think. Thanks for the advice.

BTW, anyone know of a program that will do batch file renaming. Something that will take all the files in a folder and given a wildcard like *.htm would be able to rename all of those file to filename.shtml?

Oops, never mind. Found a batch file renaming utility quite easily. Ahhh, I love when that happens. Thanks for the advice.

[This message has been edited by Maverick (edited 16 December 1999).]

Fri, 17 Dec 1999 03:32:00 +0000

Maverick,

It isn't so much the quantity of the SSI pages but rather how they are setup. SSI aren't hard on a server, even on such a large site. The problem comes when they are used improperly though. Pages that are parsed should be named accordingly. Pages with SSI should be named with the .shtml extension. I know it is a BIG convenience for users to be able to make .html pages parseable, but that is when the problems come in. If you are going to use SSI, you should use it properly by naming the file with the .shtml extension.

One of the biggest problems is search engines. Search engines go full force on .html pages because they think they are supposed to be plain text files. However, when you start parsing .html files, the search engine is still going full force on that file and thus it can cause a big problem for the server, even bringing it down in some instances. Instead, by naming the files with the .shtml extension, the search engines will slow down for them knowing there will be special coding on them and thus, much better for the server.

I hope all this made sense and enlightened your perspective of things on the host's side of this debate a little more.

------------------
Dynamic Internet Solutions : http://www.dids.com
Windows NT and UNIX Hosting