-
zope-zc.ngi-2.0.1-1.lbn25.noarch
The Network Gateway Interface provides:
* the ability to test application networking code without use of sockets, threads
or subprocesses
* clean separation of application code and low-level networking code
* a fairly simple inheritence free set of networking APIs
* an event-based framework that makes it easy to handle many simultaneous connections
while still supporting an imperative programming style.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.parse_addr-1.0.0-1.lbn13.noarch
Parse network addresses of the form: HOST:PORT
>>> import zc.parse_addr
>>> zc.parse_addr.parse_addr('1.2.3.4:56')
('1.2.3.4', 56)
It would be great if this little utility function was part of the socket module.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope-zc.parse_addr-1.0.0-1.lbn19.noarch
Parse network addresses of the form: HOST:PORT
>>> import zc.parse_addr
>>> zc.parse_addr.parse_addr('1.2.3.4:56')
('1.2.3.4', 56)
It would be great if this little utility function was part of the socket module.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope-zc.parse_addr-1.0.0-1.lbn25.noarch
Parse network addresses of the form: HOST:PORT
>>> import zc.parse_addr
>>> zc.parse_addr.parse_addr('1.2.3.4:56')
('1.2.3.4', 56)
It would be great if this little utility function was part of the socket module.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.queue-1.1-2.lbn13.noarch
Persistent queues are simply queues that are optimized for persistency
via the ZODB. They assume that the ZODB is using MVCC to avoid read
conflicts. They attempt to resolve write conflicts so that transactions
that add and remove objects simultaneously are merged, unless the
transactions are trying to remove the same value from the queue.
An important characteristic of these queues is that they do not expect to
hold more than one reference to any given equivalent item at a time. For
instance, some of the conflict resolution features will not perform
desirably if it is reasonable for your application to hold two copies of
the string "hello" within the same queue at once [1].
The module provides two flavors: a simple persistent queue that keeps all
contained objects in one persistent object (Queue), and a persistent queue
that divides up its contents into multiple composite elements
(CompositeQueue). They should be equivalent in terms of API and so are
mostly examined in the abstract in this document: we'll generate
instances with a representative Queue factory, that could be either class.
They only differ in an aspect of their write conflict resolution behavior.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope-zc.queue-2.0.0a1-1.lbn19.noarch
Persistent queues are simply queues that are optimized for persistency
via the ZODB. They assume that the ZODB is using MVCC to avoid read
conflicts. They attempt to resolve write conflicts so that transactions
that add and remove objects simultaneously are merged, unless the
transactions are trying to remove the same value from the queue.
An important characteristic of these queues is that they do not expect to
hold more than one reference to any given equivalent item at a time. For
instance, some of the conflict resolution features will not perform
desirably if it is reasonable for your application to hold two copies of
the string "hello" within the same queue at once [1].
The module provides two flavors: a simple persistent queue that keeps all
contained objects in one persistent object (Queue), and a persistent queue
that divides up its contents into multiple composite elements
(CompositeQueue). They should be equivalent in terms of API and so are
mostly examined in the abstract in this document: we'll generate
instances with a representative Queue factory, that could be either class.
They only differ in an aspect of their write conflict resolution behavior.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope-zc.queue-2.0.0-3.lbn25.noarch
Persistent queues are simply queues that are optimized for persistency
via the ZODB. They assume that the ZODB is using MVCC to avoid read
conflicts. They attempt to resolve write conflicts so that transactions
that add and remove objects simultaneously are merged, unless the
transactions are trying to remove the same value from the queue.
An important characteristic of these queues is that they do not expect to
hold more than one reference to any given equivalent item at a time. For
instance, some of the conflict resolution features will not perform
desirably if it is reasonable for your application to hold two copies of
the string "hello" within the same queue at once [1].
The module provides two flavors: a simple persistent queue that keeps all
contained objects in one persistent object (Queue), and a persistent queue
that divides up its contents into multiple composite elements
(CompositeQueue). They should be equivalent in terms of API and so are
mostly examined in the abstract in this document: we'll generate
instances with a representative Queue factory, that could be either class.
They only differ in an aspect of their write conflict resolution behavior.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.recipe.egg-1.3.2-2.lbn13.noarch
Buildout Egg-Installation Recipe
The egg-installation recipe installs eggs into a buildout eggs
directory. It also generates scripts in a buildout bin directory with
egg paths baked into them.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope-zc.recipe.egg-2.0.7-1.lbn25.noarch
Buildout Egg-Installation Recipe
The egg-installation recipe installs eggs into a buildout eggs
directory. It also generates scripts in a buildout bin directory with
egg paths baked into them.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc.recipe.egg-2.0.7-1.lbn25.noarch
Buildout Egg-Installation Recipe
The egg-installation recipe installs eggs into a buildout eggs
directory. It also generates scripts in a buildout bin directory with
egg paths baked into them.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
