|
|
.oO(tomwood2)
>Murray pointed me at SSI -Server Side Includes in another thread. But when I
>go
>to one of the books I have on Dreamweaver, the author says that my hosting
>company won't like SSI much because it uses more system resources.
True, but completely irrelevant. A truly dynmaic site with PHP and MySQL
for example requires even more resources, but after all that's what a
server is for. If the server goes down to its knees just because of a
little SSI or some scripting then you should change the host.
The server CPUs need something to do. Static HTML pages are boring. ;-)
>In response
>to that, Dreamweaver created Library items.
>
> Is there a reason to pick one method over the other?
SSI and similar techniques are processed on the server, while lib items
are more or less just replacements done in DW. If you change something,
you'd have to upload _all_ pages again, while with SSI you just upload
the one file that was modified and the server does the rest. Of course
these server-side includes/replacements happen on every single request,
but as said - it's what a server is for. You pay for it, you can use it.
Micha
|
|