Re: Benifits of ASP CMS Hosted

On Thu, 13 May 2004, Paul D. Bain wrote:
> Your statement to the contrary reveals that you know nothing of computer security.

Umm.

I'm no defender of MS infrastructure solutions (actually, I think they 
suck ass) but the personal attack because someone asserts that that stuff can 
be secured is childish. There probably are ways to secure it but let the 
fact that in the vast majority of cases people fail to secure that 
stuff speak for itself.  

Anyway, unless the question is ASP as in "Active Server Pages" and not 
"Application Service Provides" lets not degenerate a discussion of 
ASPs into a MS vs LAMP/J2EE debate on list; it's nothing directly to do 
with CMS technologies.

And On Thu, 13 May 2004, again Paul D. Bain wrote:
> At -0400Thursday 5/13/04 09:05 AM,  Michael Yacavone wrote:
> >Any decent "remote-publish" CMS is going to have incremental page
> >updating. Sure, you may occasionally need to "re-generate" the entire
> >site, but that's not the everyday operation.
> 
>          OpenCMS (at OpenCMS.org) is a damned good CMS, and it does _not_ 
> have this feature, "incremental page updating." Furthermore, I do not think 
> that Bricolage or Plone has this feature, though I am less certain of this 
> claim because I do not those CMS's as well as I know OpenCMS.

You sure are less certain.

Before roasting some poor soul about their ignorance, take a deep breath 
lest you reveal your own.  Bricolage does support incremental publishing, 
in fact that (along with flexible templating, workflow and document 
structure definition) are among the original design objectives.  When you 
say OpenCMS is "damned good" and yet it doesn't support this very basic 
feature, it makes your definition of "good" highly suspicious.  

Finally, the prior rants about having to have either the content delivery 
system close to the CMS or statically baked content is just silly.  There 
is plenty of room in between these extremes (i.e. a system could bake 
components but those components may in turn be used for request time 
frying).  Again, the "baking" versus "frying" considerations were primary 
to Bricolage's architecture.  The live-appserver-as-CMS model binds 
scaling your finished delivery systems to your data management system. And 
that's proven repeatedly over the years to fail.

-- 
Ian Kallen <spidaman _at_ arachna _dot_ com> | Yahoo/AIM: iankallen
                      http://www.arachna.com/