-
zope-zc.z3monitor-0.8.0-1.lbn13.noarch
The Zope 3 monitor server is a server that runs in a Zope 3 process and that provides
a command-line interface to request various bits of information. It is based on
zc.monitor, which is itself based on zc.ngi, so we can use the zc.ngi testing
infrastructure to demonstrate it.
This package provides several Zope 3 and ZODB monitoring and introspection tools
that work within the zc.monitor server. These are demonstrated below.
Please see the zc.monitor documentation for details on how the server works.
This package also supports starting a monitor using ZConfig, and provides a default
configure.zcml for registering plugins.
The ZConfig setup is not demonstrated in this documentation, but the usage is simple.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope-zc.z3monitor-0.8.0-1.lbn19.noarch
The Zope 3 monitor server is a server that runs in a Zope 3 process and that provides
a command-line interface to request various bits of information. It is based on
zc.monitor, which is itself based on zc.ngi, so we can use the zc.ngi testing
infrastructure to demonstrate it.
This package provides several Zope 3 and ZODB monitoring and introspection tools
that work within the zc.monitor server. These are demonstrated below.
Please see the zc.monitor documentation for details on how the server works.
This package also supports starting a monitor using ZConfig, and provides a default
configure.zcml for registering plugins.
The ZConfig setup is not demonstrated in this documentation, but the usage is simple.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope-zc.z3monitor-0.8.0-1.lbn25.noarch
The Zope 3 monitor server is a server that runs in a Zope 3 process and that provides
a command-line interface to request various bits of information. It is based on
zc.monitor, which is itself based on zc.ngi, so we can use the zc.ngi testing
infrastructure to demonstrate it.
This package provides several Zope 3 and ZODB monitoring and introspection tools
that work within the zc.monitor server. These are demonstrated below.
Please see the zc.monitor documentation for details on how the server works.
This package also supports starting a monitor using ZConfig, and provides a default
configure.zcml for registering plugins.
The ZConfig setup is not demonstrated in this documentation, but the usage is simple.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.zk-1.2.0-1.lbn13.noarch
The zc.zk package provides some high-level interfaces to the low-level zookeeper extension. It's not complete, in that it doesn't try, at this time, to be a complete high-level interface. Rather, it provides facilities we need to use ZooKeeper to connect services:
ZODB database clients and servers
HTTP-based clients and services
Load balancers and HTTP application servers
The current (initial) use cases are:
Register a server providing a service.
Get the addresses of servers providing a service.
Get and set service configuration data.
Model system architecture as a tree.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope-zc.zk-1.2.0-1.lbn19.noarch
The zc.zk package provides some high-level interfaces to the low-level zookeeper extension. It's not complete, in that it doesn't try, at this time, to be a complete high-level interface. Rather, it provides facilities we need to use ZooKeeper to connect services:
ZODB database clients and servers
HTTP-based clients and services
Load balancers and HTTP application servers
The current (initial) use cases are:
Register a server providing a service.
Get the addresses of servers providing a service.
Get and set service configuration data.
Model system architecture as a tree.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope-zc.zk-1.2.0-1.lbn25.noarch
The zc.zk package provides some high-level interfaces to the low-level zookeeper extension. It's not complete, in that it doesn't try, at this time, to be a complete high-level interface. Rather, it provides facilities we need to use ZooKeeper to connect services:
ZODB database clients and servers
HTTP-based clients and services
Load balancers and HTTP application servers
The current (initial) use cases are:
Register a server providing a service.
Get the addresses of servers providing a service.
Get and set service configuration data.
Model system architecture as a tree.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.zkzeo-0.3.2-1.lbn13.noarch
Managing addresses, and especially ports is a drag. ZooKeeper can be used as a service registry. Servers can register themselves and clients can find services there. The zc.zkzeo package provides support for registering ZEO servers and a ZEO client storage that gets addresses from ZooKeeper.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope-zc.zkzeo-0.3.2-1.lbn19.noarch
Managing addresses, and especially ports is a drag. ZooKeeper can be used as a service registry. Servers can register themselves and clients can find services there. The zc.zkzeo package provides support for registering ZEO servers and a ZEO client storage that gets addresses from ZooKeeper.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope-zc.zkzeo-0.3.2-1.lbn25.noarch
Managing addresses, and especially ports is a drag. ZooKeeper can be used as a service registry. Servers can register themselves and clients can find services there. The zc.zkzeo package provides support for registering ZEO servers and a ZEO client storage that gets addresses from ZooKeeper.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.zkzopeserver-1.3.2-1.lbn13.noarch
zc.zkzopeserver provides a wrapper for the zope.server WSGI runner that registers with ZooKeeper. By registering with ZooKeeper, you can let the operating system assign ports and have clients find your server by looking in ZooKeeper.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
