Re: Using SSI versus Dreamweaver Library items.

["Murray *ACE*" <forums@xxxxxxxxxxxxxxxxxxxxxxxx>]

> Murray - Was there a reason you didn't recommend Dreamweaver Library items 
> for
> common elements across a lot of pages?

Micha touched on the highpoints.  For me, the argument about system 
resources on servers is sooo 1980s, and the convenience of making a change 
to a single file which is uploaded as opposed to every local file needing to 
be uploaded swings the balance.  Hosts nowadays accept that SSI is the way 
to go, and will never complain.  If you have sources that continue to press 
that argument, you can be sure that the source is so out of date as to be 
useless....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"tomwood2" <webforumsuser@xxxxxxxxxxxxxx> wrote in message 
news:g5nrav$t$1@xxxxxxxxxxxxxxxxxxxxxxxx
> 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. In 
> response
> to that, Dreamweaver created Library items.
>
> Is there a reason to pick one method over the other?
>
> Murray - Was there a reason you didn't recommend Dreamweaver Library items 
> for
> common elements across a lot of pages?
>
> Thanks,
>
> Tom