Re: Benifits of ASP CMS Hosted

From: "Michael Yacavone" <[email protected]>
> I can probably answer the question for Plone if somebody tells me
> what a "remote-publish CMS" is and what the heck "incremental page
> updating" is, and why you would want it. :-)

> In the context of Mr. Bain's argument, "remote-publish" simply means the
> CMS ftp's or sftp's the static html files to another server for web
> hosting.

Plone does not have a button to do this, as Frontpage has, for example.
However, there are many different ways of doing this, from different types
of caching, to scripting, to adding a button to do it.

> "Incremental page updating" just means that you can publish one
> page (or group of pages) at a time, rather than pushing the whole site out
> for minor page updates.

> You would want these two features because separating the data-management
> system (with it's many moving parts) and the web page delivery system will
> scale better and much cheaper. And as a site grows, you don't want to ftp
> a whole site with thousands of pages just because someone fixed a typo
> somewhere.

Ah, well that is just a case of comparing some dates dates when doing the
update, so that it obviously trivial.


This is indeed somewhat of a basic feature when you are using web-CMS's for
updating "static" company websites. It is my impression that open source
CMS's are rarely used for this, but are rather used for building dymanic
content management systems, such as intranets or community sites or sites
that are constantly updated such as news sites.

They are also used for smaller websites because they are cheap, and then
performance tends not to be a problem, so static publishing is seen as an
extra useless nuisance. :-)

I could be wrong, it is just the impression I have.