On Sat, 10 Jun 2006 04:24:16 -0700, IT Office WCSC
<[EMAIL PROTECTED]> wrote:
I think the steep costs of the Plone hosting solutions is due to the huge
resource demands made by the zope/plone stack on the server in terms of
mainly memory and processing power to a lesser extent. Making Plone less
resource hungry - as light as a breeze - will help in reducing the costs.
It is also impossible because of the way Zope and Plone works. It's not
simple PHP script files doing single queries against a relational DB.
Plone isn't constructed to be an ASP solution, and probably never will be
either.
I
think work is already going on in this end with integrating CacheFu with
Plone ... and there might be several efforts on the zope side. This would
benefit not only the NGO segment but the whole Plone community as well.
CacheFu uses more memory, not less - but gives a significant speed boost.
And I think that making the installing and esp. the maintenance and
upgrading less labour intensive will further improve the readiness of the
hosting companies and reduce the costs. This would include some automatic
patch management system in case of security patches and easier upgrading
cycles.
This will become more sane in the future thanks to GenericSetup and other
Zope 3 machinery.
--
_____________________________________________________________________
Alexander Limi · Chief Architect · Plone Solutions · Norway
Consulting · Training · Development · http://www.plonesolutions.com
_____________________________________________________________________
Plone Co-Founder · http://plone.org · Connecting Content
Plone Foundation · http://plone.org/foundation · Protecting Plone
_______________________________________________
NGO mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/ngo
