plone

zope.minmax-2.1.0-1.lbn25.noarch
This package provides support for homogeneous values favoring maximum or minimum for ZODB conflict resolution. See src/zope/minmax/minmax.txt for a detailed description.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.mkzeoinstance-4.1-1.lbn25.noarch
This package provides a single script, mkzeoinstance, which creates a standalone ZEO server instance.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.modulealias-3.4.0-4.lbn25.noarch
Zope modulealias
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.pagetemplate-4.4.1-1.lbn25.noarch
Page Templates provide an elegant templating mechanism that achieves a clean separation of presentation and application logic while allowing for designers to work with templates in their visual editing tools (FrontPage, Dreamweaver, GoLive, etc.). Detailed Documentation ZPT (Zope Page-Template) Architecture There are a number of major components that make up the page-template architecture: The TAL compiler and interpreter. This is responsible for compiling source files and for executing compiled templates. See the zope.tal package for more information. An expression engine is responsible for compiling expressions and for creating expression execution contexts. It is common for applications to override expression engines to provide custom expression support or to change the way expressions are implemented. The zope.app.pagetemplate package uses this to implement trusted and untrusted evaluation; a different engine is used for each, with different implementations of the same type of expressions. Expression contexts support execution of expressions and provide APIs for setting up variable scopes and setting variables. The expression contexts are passed to the TAL interpreter at execution time. The most commonly used expression implementation is that found in zope.tales. Page templates tie everything together. They assemble an expression engine with the TAL interpreter and orchestrate management of source and compiled template data. See zope.pagetemplate.interfaces.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.password-4.2.0-2.lbn25.noarch
This package provides a password manager mechanism. Password manager is an utility object that can encode and check encoded passwords.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.pluggableauth-2.1.0-2.lbn25.noarch
Based on zope.authentication, this package provides a flexible and pluggable authentication utility, and provides a number of common plugins. Pluggable-Authentication Utility The Pluggable-Authentication Utility (PAU) provides a framework for authenticating principals and associating information with them. It uses plugins and subscribers to get its work done. For a pluggable-authentication utility to be used, it should be registered as a utility providing the zope.authentication.interfaces.IAuthentication interface. Authentication The primary job of PAU is to authenticate principals. It uses two types of plug-ins in its work: Credentials Plugins Authenticator Plugins Credentials plugins are responsible for extracting user credentials from a request. A credentials plugin may in some cases issue a ‘challenge’ to obtain credentials. For example, a ‘session’ credentials plugin reads credentials from a session (the “extraction”). If it cannot find credentials, it will redirect the user to a login form in order to provide them (the “challenge”). Authenticator plugins are responsible for authenticating the credentials extracted by a credentials plugin. They are also typically able to create principal objects for credentials they successfully authenticate. Given a request object, the PAU returns a principal object, if it can. The PAU does this by first iterating through its credentials plugins to obtain a set of credentials. If it gets credentials, it iterates through its authenticator plugins to authenticate them. If an authenticator succeeds in authenticating a set of credentials, the PAU uses the authenticator to create a principal corresponding to the credentials. The authenticator notifies subscribers if an authenticated principal is created. Subscribers are responsible for adding data, especially groups, to the principal. Typically, if a subscriber adds data, it should also add corresponding interface declarations.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.preference-3.8.0-2.lbn25.noarch
User Preferences Framework
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.principalannotation-4.1.1-1.lbn25.noarch
This package implements annotations for zope.security principals. Common annotation techniques, like AttributeAnnotations cannot be applied to principals, since they are created on the fly for every request. Principal Annotations This package implements annotations for zope.security principals. To make it clear, the principal here is the object that provides zope.security.interfaces.IPrincipal interface and annotations is the object providing zope.annotation.interfaces.IAnnotations. The problem is that principals is dynamic, non-persistent objects created on the fly for every security participation (request or something), so common annotation techniques, like AttributeAnnotations cannot be applied to them. This package provides a persistent storage of principal annotations, storing annotations by principal ID as well as an adapter from IPrincipal to IAnnotations.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.principalregistry-3.7.1-2.lbn25.noarch
zope.principalregistry
Located in LBN / … / Plone and Zope / BastionLinux 25
zope.processlifetime-2.1.0-1.lbn25.noarch
This package provides interfaces / implementations for events relative to the lifetime of a server process (startup, database opening, etc.) It is derived from Zope 3.4’s zope.app.appsetup.
Located in LBN / … / Plone and Zope / BastionLinux 25

« Previous 10 items Next 10 items » 1 ... 2314 2315 2316 2317 2318 2319 2320 ... 4849

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.