Great idea, but this could also be a chance to fix the windows z2.py
thang and the installer ;)
Maybe, but I have no expertise in this area.
As long as standalone Zope without ZEO would still be a startup
option, Im sure there are more things out there like the Plone
Controller that might
IMHO, Zope releases should, in this scenario, be configured by default to
use a custom_zodb.py file with ClientStorage over a socket at startup,
making the default config of Zope one that uses ZEO. Also, start scripts
should be distributed with options to support both the following:
-
take a while to catch up.
--
Andy McKay
www.agmweb.ca
- Original Message -
From: Guido van Rossum [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 02, 2002 11:26 AM
Subject: [Zope-dev] Integrating ZEO with Zope 2.7
We're close to finishing a new version of ZEO, which
On Wednesday 02 Oct 2002 8:03 pm, [EMAIL PROTECTED] wrote:
+1
+1
IMHO, Zope releases should, in this scenario, be configured by default to
use a custom_zodb.py file with ClientStorage over a socket at startup,
That is a tempting idea.
Use of a TCP socket has security implications that make
: [Zope-dev] Integrating ZEO with Zope 2.7
On Wednesday 02 Oct 2002 8:03 pm, [EMAIL PROTECTED] wrote:
+1
+1
IMHO, Zope releases should, in this scenario, be configured by default to
use a custom_zodb.py file with ClientStorage over a socket at startup,
That is a tempting idea.
Use of a TCP
On Wed, 2002-10-02 at 16:03, [EMAIL PROTECTED] wrote:
+1
+1 for me too
IMHO, Zope releases should, in this scenario, be configured by default to
use a custom_zodb.py file with ClientStorage over a socket at startup,
making the default config of Zope one that uses ZEO.
I'm not sure about
On Wednesday 02 Oct 2002 8:50 pm, [EMAIL PROTECTED] wrote:
Hmm... My thought: on Win32, bind the TCP port to the loopback address.
Since Win32 in _most_ cases is not a multi-user system, this would have the
general effect of keeping this from being an issue (unless you ran terminal
services
IMHO, Zope releases should, in this scenario, be configured by default to
use a custom_zodb.py file with ClientStorage over a socket at startup,
That is a tempting idea.
Use of a TCP socket has security implications that make it a bad
choice for a default, unless we implement mutual
