Greetings!
On 22 Mar, Alessandro Bottoni wrote:
> Interesting topic!
Yes, and one where it is hard to find definite answers
on. I'd advice on using the one that you feel more
comfortable with.
You can find some slightly aged discussion
about the differences between Midgard and
Zope from DevShed:
http://www.devshed.com/Server_Side/PHP/Midgard/
> How does Zope compare with Midgard?
Generally, Zope is more object-oriented, while
Midgard takes a more traditional approach to
handling its data. The new OOP-style extensions
in the upcoming Midgard 1.4 will change this
somewhat, but the base idea still remains.
Zope also is slightly older product, and has
more support.
> Which one is more flexible (that is: which one can be used in a wider set of
> cases)?
Zope uses Python, which is a real programming
languages, where PHP is mostly confined to only
Web scripting. Because of this, Zope is more
extensible. However, as both can easily use
external programs by running commands or sending
XML-RPC requests, this isn't much of a problem.
> Which one is easier to learn for the webmaster?
This depends on what kind of development experience
the Webmaster has. Midgard's templating concept is
quite near how SSI works, and the PHP syntax is pretty
similar to Perl.
I don't have enough Zope experience to actually say
anything conclusive about this.
> Which one is better fit to develop and maintain a complex web site (let's
> say: 10,000 documents and 50,000 pictures, updated weekly)?
Here I'm inclined to say Midgard. If you're working
with a large site, it is very easy to write a custom
administration interface for that, making the maintenance
workload very bearable.
As an example, we developed a custom content management
solution with Midgard for Stonesoft, and now practically
everybody who deals with publishable content in the
organization handles his part of maintenance himself,
enabling our Web team to concentrate on writing new
applications instead.
> Which one is better for web sites that uses database and/or a "fragmented
> document" architecure (XML/SGML documents that are disassembled and
> re-assembled on demand)?
Midgard uses its own database format, but you also have
the complete PHP database and XML connectivity available.
I can't comment on how Zope handles this.
> Which one can better integrate other technologies (web-mail interfaces and
> so on)?
I've seen a couple of Webmail interfaces available for
PHP, so those can also be used with Midgard. Also, see
my answer on flexibility.
> Which one is easier to use for a remote customer, enabled to develop and
> maintain his pages on the server?
Both use a Web-based administration interface, so this
shouldn't be a problem with either. With Midgard, you
it is also easy to host many sites on the same server.
For example, the server which hosts the Midgard project
Web site hosts about dozen Midgard-based sites in total,
and all of these are administrated remotely.
> Which one is better for "workgroup" intranet servers?
I've implemented a couple of these quite easily
with Midgard.
> Which one is safer (more anti-hacker)?
With Midgard, you can use all normal Apache security
techniques (SSL, etc.)
> Which features does Zope have that Midgard does not have?
At least two come to mind, complete object-orientedness
and native database searching.
However, you can use external search engines with Midgard.
> PS What does "Midgard" mean (I'm italian...)?
It is a name. Midgard was the place where humans
lived (as opposed to realms of gods or giants) in
the Norse mythology.
> Alessandro Bottoni ([EMAIL PROTECTED])
/Bergie
--
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
http://www.iki.fi/Henri.Bergius
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
