Discuss mailing list

[Niels Dettenbach <nd AT syndicat.com>]

Am Dienstag, 21. Februar 2012, 12:42:51 schrieb Richard Lyons:
> Typo3 might be a more accessible alternative. 
...we have many users / customers formerly used Typo3 or other LAMP based "so 
called CMS" (coming to it as the Typo3 hype was going on) switching over to 
ine of the Zope based CMS or web app solutions, but no one who was switching 
vice versa. The half of them has technically (very) skilled staff - the 
others 
compeletly not - but all of them are managing their websites really byself - 
not let do this any skilled people.

Most of them could shrink their man power ressources to maintain their web 
content very significantly - and this is what typical company customer want. 
The other point for him is to how flexible he can realize new business 
processes and ideas within his websites, how long does it takes and how much 
does it costs.

Most of them don't want to waste time and costs with fiddeling with any 
system 
they need educated peoples or at least a skilled techi to handle it. A CMS 
should be as easy that every non educated people should be able to manage 
content. Typo3 is this - by my experience - not. Most customers of Typo3 
websites has i.e. a techi in their house or just leave that job to any 
skilled 
agency.

Beside this we had/have many customers who run into performance or 
scalability 
problems with Typo3 even if their website just has to handle 2 or 3 pages per 
second on their hosts. Performance opmtimizing of Typo3 is a tricky thing by 
itself and generates costs for the owner - but if he did not had significant 
load this did not makes any real sense...

One of the customers developed a "portal version" of Typo3 with a lot of man 
power and costs - to run and maintain some hundreds of Typo3 websites of 
suborganisations of an organisation with one of a selection of themes and 
partly own, partly central maintained content. This all has to be done by 
special and complex programmings changing most time a new Typo3 versions 
comes 
out aso..
The result is widely a bunch of frickeled / hacked together php and shell 
code 
which could only be maintained by high level experts of this special 
solution. 
Another point was to "cluster" that setup because of performance lacks. 


With zope / zodb this all is mainly just some clicks or simple setup tasks 
far 
if qometimes required. Generating a new instance of a website i.e. is just a 
click wide. I.e. mirroring or clustering a Plone based OpenNIC website could 
be comparavly easily done by clustering the ZODB and the http frontends - 
i.e. 
with nginx or even apache or by DNS.

The conversion of relational data objects / rows into typically oo web 
objects 
or vice versa generates the most of processing overhead within typical LAMP 
based web CMS systems (did not know any real CMS in PHP - even if the owners 
of Typo3 means their system is a "enterprise CMS" - it is not...). Web 
content 
usually is not relationale - so why using a RDBMS with up to hundreds of SQL 
requests to generat asingle website?

 As all of the Typo3 "engineers" was on its skilled end we taked over the 
system management behind on their machines to fiddle out performance lacks as 
far as possible...

Not at least: How does your "WCMS" Typo3 and/or Wordpress stores content? 

No, WP and Typo3 data are just tables just working and fitting the needs of 
their applications.

Very differently from such LAMP WCMS apps in Zope / Plone / ZMS content could 
be exported i.e. into a XML stream or another format which lets you the 
option 
to import it into another solution? Transferring a complete website incl. 
theming, hiostory etc. is just cklicking export on the source and import on 
the second Zope / Plone host. You may export is as static HTML or into other 
formats by media filters etc.


best regards,


Niels.

-- 
---
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com/

Attachment: signature.asc
Description: This is a digitally signed message part.