-
zope.session-4.1.0-2.lbn25.noarch
Sessions provide a way to temporarily associate information with a client without requiring the authentication of a principal. We associate an identifier with a particular client. Whenever we get a request from that client, we compute the identifier and use the identifier to look up associated information, which is stored on the server.
A major disadvantage of sessions is that they require management of information on the server. This can have major implications for scalability. It is possible for a framework to make use of session data very easy for the developer. This is great if scalability is not an issue, otherwise, it is a booby trap.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.site-3.9.2-2.lbn13.noarch
Local registries for zope component architecture
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.site-4.2.2-1.lbn25.noarch
This package provides a local and persistent site manager implementation, so that one can
register local utilities and adapters. It uses local adapter registries for its adapter
and utility registry. The module also provides some facilities to organize the local
software and ensures the correct behavior inside the ZODB.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.site-4.2.2-1.lbn25.noarch
This package provides a local and persistent site manager implementation, so that one can
register local utilities and adapters. It uses local adapter registries for its adapter
and utility registry. The module also provides some facilities to organize the local
software and ensures the correct behavior inside the ZODB.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.size-3.4.1-5.lbn13.noarch
This package provides a definition of simple interface that allows to
retrieve the size of the object for displaying and for sorting.
The default adapter is also provided. It expects objects to have the getSize
method that returns size in bytes, however, it won't crash if an object doesn't
have one and will show size as not available instead.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.size-4.1.0-1.lbn25.noarch
This package provides a definition of simple interface that allows to
retrieve the size of the object for displaying and for sorting.
The default adapter is also provided. It expects objects to have the getSize
method that returns size in bytes, however, it won't crash if an object doesn't
have one and will show size as not available instead.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.size-4.1.0-1.lbn25.noarch
This package provides a definition of simple interface that allows to
retrieve the size of the object for displaying and for sorting.
The default adapter is also provided. It expects objects to have the getSize
method that returns size in bytes, however, it won't crash if an object doesn't
have one and will show size as not available instead.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.sqlalchemy-0.6.1-3.lbn13.noarch
The aim of this package is to unify the plethora of existing packages integrating
SQLAlchemy with Zope's transaction management. As such it seeks only to provide a
data manager and makes no attempt to define a zopeish way to configure engines.
For WSGI applications, Zope style automatic transaction management is available
with repoze.tm2, a part of Repoze BFG and Turbogears 2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.sqlalchemy-0.6.1-4.lbn19.noarch
The aim of this package is to unify the plethora of existing packages integrating
SQLAlchemy with Zope's transaction management. As such it seeks only to provide a
data manager and makes no attempt to define a zopeish way to configure engines.
For WSGI applications, Zope style automatic transaction management is available
with repoze.tm2, a part of Repoze BFG and Turbogears 2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.sqlalchemy-0.7.7-1.lbn25.noarch
The aim of this package is to unify the plethora of existing packages integrating
SQLAlchemy with Zope's transaction management. As such it seeks only to provide a
data manager and makes no attempt to define a zopeish way to configure engines.
For WSGI applications, Zope style automatic transaction management is available
with repoze.tm2, a part of Repoze BFG and Turbogears 2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
