Forum OpenACS Q&A: Re: Evaluating Web Publishing frameworks

Posted by Torben Brosten on
For the record, here's the reference to the above quote:

Here are my notes from reading these slides:

It would have been nice to have a breakdown of the weaknesses of tcl and AOLserver as was done for PHP on the following slide:

tcl+aolserver+openacs doesn't have the PHP weaknesses as far as I understand them.  Nor does the openacs api have the weaknesses outlined with java api here:

or the perl api here:

or mod_perl here:

or dbi here:

In fact, "they" seem interested in using PostgreSQL here:

Maybe this criticism of apache+mod_perl has some insight into why tcl+aolserver+openacs was not chosen: not enough of a mature "CPAN"ish tcllib?

These comments about their future plans seem similar to some current openacs functionality (rss?) and the xlm parcer and discussions that are going on here (now) regarding xml, xslt etc:

The reasons for not using ZOPE are interesting.. at least the part about ZOPE re-creating internal sw instead of integrating with other components:

My question:

Is this MASON technology similar to the "include" tag functionality in the openacs templating system?