-
zope-zc.sourcefactory-0.7.0-2.lbn25.noarch
An easy way to create custom Zope 3 sources.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.testbrowser-1.0.0a5-4.lbn25.noarch
The zc.testbrowser package provides web user agents (browsers) with
programmatic interfaces designed to be used for testing web applications,
especially in conjunction with doctests.
There are currently two type of testbrowser provided. One for accessing web
sites via HTTP (zc.testbrowser.browser) and one that controls a Firefox web
browser (zc.testbrowser.real). All flavors of testbrowser have the same API.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.thread-0.1.0-1.lbn25.noarch
The thread-creation API provided by the Python threading module is annoying. :)
This package provides a very simple thread-creation API that:
Makes threads daemonic and allows daemonicity to be passed to the constructor. For example:
zc.thread.Thread(mythreadfunc)
Starts a daemonic thread named 'mythreadfunc' running mythreadfunc.
Allows threads to be defined via decorators, as in:
import zc.thread
@zc.thread.Thread
def mythread():
...
In the example above, a daemonic thread named mythread is created and started. The thread is also assigned to the variable mythread.
You can control whether threads are daemonic and wether they are started by default:
import zc.thread
@zc.thread.Thread(daemon=False, start=False)
def mythread():
...
After a thread finishes, you can get the return value of the target function from the thread's value attribute, or, if the function raises an exception, you can get the exception object from the thread's exception attribute. (This feature was inspired by the same feature in gevent greenlets.)
There's also a Process constructor/decorator that works like Thread, but with multi-processing processes, and without the value and exception attributes.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.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.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.lbn25.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 25
-
zope-zc.zrs-3.1.0-1.lbn25.noarch
ZODB replicated storage (ZRS) provides database replication for ZODB. For each database, a primary storage and one or more secondary storages may be defined. The secondary storages will automatically replicate data from the primary storage.
Replication is superior to back-ups because as long as secondaries are running, secondary data is kept updated. In the event of a failure of a primary storage, just reconfigure a secondary to be the primary, and it can begin handling application requests.
Features
Primary/secondary replication
Support for read-only secondary storages
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zeo-2.13.30-3.lbn25.noarch
This package contains the ZEO server and necessary startups
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zeo-2.13.30-3.lbn25.noarch
This package contains the ZEO server and necessary startups
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
