-
zope.securitypolicy-4.1.0-1.lbn25.noarch
This package implements a role-based security policy similar to the policy found in Zope 2. The security policy is responsible for deciding whether an interaction has a permission on an object. This security policy does this using grant and denial information. Managers can grant or deny:
roles to principals,
permissions to principals, and
permissions to roles
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.sendmail-4.0.1-2.lbn25.noarch
zope.sendmail is a package for email sending from Zope 3 applications. Email sending from Zope 3
applications works as follows:
A Zope 3 application locates a mail delivery utility (IMailDelivery) and feeds a message to it.
It gets back a unique message ID so it can keep track of the message by subscribing to IMailEvent
events.
The utility registers with the transaction system to make sure the message is only sent when the
transaction commits successfully. (Among other things this avoids duplicate messages on ConflictErrors.)
If the delivery utility is a IQueuedMailDelivery, it puts the message into a queue (a Maildir
mailbox in the file system). A separate process or thread (IMailQueueProcessor) watches the queue and
delivers messages asynchronously. Since the queue is located in the file system, it survives Zope
restarts or crashes and the mail is not lost. The queue processor can implement batching to keep
the server load low.
If the delivery utility is a IDirectMailDelivery, it delivers messages synchronously during the
transaction commit. This is not a very good idea, as it makes the user wait. Note that transaction
commits must not fail, but that is not a problem, because mail delivery problems dispatch an event
instead of raising an exception.
However, there is a problem – sending events causes unknown code to be executed during the
transaction commit phase. There should be a way to start a new transaction for event processing
after this one is commited.
An IMailQueueProcessor or IDirectMailDelivery actually delivers the messages by using a mailer (IMailer)
component that encapsulates the delivery process. There currently is only one mailer:
ISMTPMailer sends all messages to a relay host using SMTP.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.sequencesort-4.0.1-1.lbn25.noarch
This package provides support for sorting sequences based on multiple keys, including locale-based comparisons and per-key directions.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.server-3.9.0-1.lbn25.noarch
This package contains generic base classes for channel-based servers, the servers themselves and
helper objects, such as tasks and requests.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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 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 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 25
-
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
-
zope.structuredtext-4.1.0-1.lbn25.noarch
This package provides a parser and renderers for the classic Zope “structured text” markup
dialect (STX). STX is a plain text markup in which document structure is signalled primarily
by identation
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.tal-4.4-1.lbn25.noarch
The Zope3 Template Attribute Languate (TAL) specifies the custom namespace
and attributes which are used by the Zope Page Templates renderer to inject
dynamic markup into a page. It also includes the Macro Expansion for TAL
(METAL) macro language used in page assembly.
The dynamic values themselves are specified using a companion language,
TALES (see the 'zope.tales' package for more).
See: http://www.zope.org/Wikis/DevSite/Projects/ZPT/TAL%20Specification%201.4
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
