<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000066">
<font size="-1"><font face="Verdana">FYI,<br>
<br>
Back during 2.6.x, I developed my whole system on a Windows Laptop,
migrated to a Windows ZEO System, 1 client, 1 server. Then moved the
ZEO client & server to Red Hat AS 2.1, and now finally to SuSE
9.0. The only differences for me were the steps in installing PIL
(Python Imaging Library) on Linux vs. Windows. I had to wait to be
more comfortable deploying on Linux, but Zope was obviously ready for
Linux long before I was.<br>
<br>
If you can stay away from platform-dependent products, and their
dependencies, (Photo Product & ImageMagick for one), you should be
able to mix and match. The underlying python seems to facilitate this
being a sort of intermediary compatibilty layer. My approach was to
make sure every component and dependency was python based.<br>
<br>
Make sure to follow the directions for ZEO client/server compatibility,
but those are python concerns. <br>
<br>
As for performance, I found Linux to be a large boost, especially when
run without a GUI... the nature of the beast seems to lean toward Linux
for good reason.<br>
<br>
The other item you'll find on the list, is that a ZEO configuration is
much more stable and forgiving than the quite-stable stand-alone Zope.
Even internal Zope routines run better in a ZEO setup. <br>
<br>
-Jon Cyr<br>
WeddingWeblog.com<br>
</font></font><br>
J Cameron Cooper wrote:<br>
<blockquote cite="mid426FBD8F.6040503@jcameroncooper.com" type="cite">ken
wood wrote:
<br>
<br>
<blockquote type="cite">I appreciate all the great tips on the
cionfiguration issue. But my main issue is about infrastructure:
<br>
Which hardware and / or operating systems can be used for a Zope/Zeo
system.
<br>
</blockquote>
<br>
OS: pretty much any Unixish OS, though on anything but Linux, BSD, and
Mac OS X (and maybe Solaris) you may run into some small problems. Also
Windows.
<br>
<br>
Hardware: anything with enough juice that can run your OS. Not very
specific, I know, but it all depends on the performance you need. Less
than .5 hits/sec and pretty much anything that'll load Zope will work.
<br>
<br>
<blockquote type="cite">In particular, can I run a Zope instance on
my Win32 server and have a Zeo Server/Clients on my Linux server?
<br>
</blockquote>
<br>
Sure. Why not?
<br>
<br>
<blockquote type="cite">If I use all the same versions (Python, Zope
and Plone and Products) can I use a multi-OS infratructure?
<br>
</blockquote>
<br>
Almost certainly. There are a few OS-specific Products, though, but
that only matters on the ZEO client (except for storages, which only
matter on the ZEO server.)
<br>
<br>
You don't even have to match versions, save for sanity. ZEO is not a
tightly-coupled communications protocol. Consider:
<br>
<br>
Windows
<br>
Python 2.3.4
<br>
Zope 2.7.5
<br>
ZEO client - SomeProduct 1.1
<br>
<br>
Linux
<br>
Python 2.3.3
<br>
Zope 2.7.3
<br>
ZEO server - no products
<br>
ZEO client - SomeProduct 1.0
<br>
ZEO command line client, for debugging
<br>
<br>
This would work fine. All three ZEO clients would have the same data
(that from the ZEO server), even with different software.
<br>
<br>
--jcc
<br>
_______________________________________________
<br>
Zope maillist - <a class="moz-txt-link-abbreviated" href="mailto:Zope@zope.org">Zope@zope.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://mail.zope.org/mailman/listinfo/zope">http://mail.zope.org/mailman/listinfo/zope</a>
<br>
** No cross posts or HTML encoding! **
<br>
(Related lists - <a class="moz-txt-link-freetext" href="http://mail.zope.org/mailman/listinfo/zope-announce">http://mail.zope.org/mailman/listinfo/zope-announce</a>
<br>
<a class="moz-txt-link-freetext" href="http://mail.zope.org/mailman/listinfo/zope-dev">http://mail.zope.org/mailman/listinfo/zope-dev</a> )
<br>
<br>
<br>
</blockquote>
</body>
</html>