plone

zope.sequencesort-3.4.0-4.lbn13.noarch
zope.sequencesort
Located in LBN / … / Plone and Zope / BastionLinux 13
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.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 19
zope.server-3.6.3-2.lbn13.noarch
zope.server
Located in LBN / … / Plone and Zope / BastionLinux 13
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.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 19
zope.session-3.9.5-2.lbn13.noarch
zope.session
Located in LBN / … / Plone and Zope / BastionLinux 13
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.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

« Previous 10 items Next 10 items » 1 ... 4884 4885 4886 4887 4888 4889 4890 ... 4897

Sections

Search results


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