Hello Chris, 1. Thank you very much! 2. Since I am planing to run two zope clients on the same (dual processor) machine, I think that it is better to use socket (faster) instead of tcp/ip. Is that correct? 3. You said that the 'socket-name' key in the <runner> section is not related to ZEO... but what is the <runner> section for? Thank you again! Michele
I'm trying to configure Zope-2.7.3 with ZEO (this is my first experience with Zope > 2.5.x) and I read somewhere that in the configuration file 'zeo.conf' in the <zeo>-section you can set the key 'address' to a 'host:port' pair or a 'unix domain socket'.
Yup. If that's true (I haven't read the config file), a "host:port" pair means e.g. "localhost:9999", while a "unix domain socket" would be something like "/a/path/to/zeo.sock'
In the <runner>-section there is also a 'socket-name' key, that's default value is '$INSTANCE/etc/zeo.zdsock'.
Now: what is the difference between the 'address' (when set to a socket) and the 'socket-name'? And where has the zope-client to 'point to'? address od socket-name?
The 'socket-name' key in the <runner> section is not related to ZEO. Ignore it.
The 'address' when set to a unix domain socket value needs to point to the socket file that the ZEO server creates (if it is configured to do so; it has its own configuration file). The 'address', when set to a "hostname:port" setting must point to the host name and port on which the ZEO server is listening (again, see the ZEO server configuration).
- C