15 Aug
2007
15 Aug
'07
1:37 p.m.
My idea is to use *both*. Plone and Seaside. Use Plone
for everything
that's easy to use out of the box and use Seaside for requirements
that
would need special python programming. It should be possible to bring
both together with either http://plone.org/products/htmlproxy (a proxy
based integration) or http://plone.org/products/windowz/releases
(iFrame
based integration). I haven't tried this approach but it's on my
todo list.
I've done several proxy based integrations with Zope and Seaside.
This works nicely and is completely transparent, as both application
servers are mostly run behind Apache anyway. A visitor can't tell the
difference of the Zope and Seaside parts, except by looking at the
URL parameters.
Eventually I moved everything to SmallWiki (the Pier at that time).
I don't see that Pier can reach the the
functionality that Plone
delivers today in near or mid future.
What are the missing parts in Seaside (vs. Zope) and Pier (vs. Plone)
then?
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch