-
repoze.vhm-0.14-1.lbn19.noarch
This package provides middleware and utilities for doing virtual
hosting within a WSGI/Repoze environment. It is particularly
useful within a 'repoze.zope2' environment, where it may be used
as an alternative to the classic
"VirtualHostMonster":http://www.zope.org/Members/4am/SiteAccess2/info
method of doing virtual hosting.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
repoze.vhm-0.14-1.lbn25.noarch
This package provides middleware and utilities for doing virtual
hosting within a WSGI/Repoze environment. It is particularly
useful within a 'repoze.zope2' environment, where it may be used
as an alternative to the classic
"VirtualHostMonster":http://www.zope.org/Members/4am/SiteAccess2/info
method of doing virtual hosting.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
repoze.who-2.0-2.lbn13.noarch
``repoze.who`` is an identification and authentication framework
for arbitrary WSGI applications. It acts as WSGI middleware.
``repoze.who`` is inspired by Zope 2's Pluggable Authentication
Service (PAS) (but ``repoze.who`` is not dependent on Zope in any
way; it is useful for any WSGI application). It provides no
facility for authorization (ensuring whether a user can or cannot
perform the operation implied by the request). This is considered
to be the domain of the WSGI application.
It attemtps to reuse implementations from ``paste.auth`` for some
of its functionality.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
repoze.who-2.3-1.lbn25.py37.noarch
``repoze.who`` is an identification and authentication framework
for arbitrary WSGI applications. It acts as WSGI middleware.
``repoze.who`` is inspired by Zope 2's Pluggable Authentication
Service (PAS) (but ``repoze.who`` is not dependent on Zope in any
way; it is useful for any WSGI application). It provides no
facility for authorization (ensuring whether a user can or cannot
perform the operation implied by the request). This is considered
to be the domain of the WSGI application.
It attemtps to reuse implementations from ``paste.auth`` for some
of its functionality.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
repoze.who-2.3-1.lbn25.py37.noarch
``repoze.who`` is an identification and authentication framework
for arbitrary WSGI applications. It acts as WSGI middleware.
``repoze.who`` is inspired by Zope 2's Pluggable Authentication
Service (PAS) (but ``repoze.who`` is not dependent on Zope in any
way; it is useful for any WSGI application). It provides no
facility for authorization (ensuring whether a user can or cannot
perform the operation implied by the request). This is considered
to be the domain of the WSGI application.
It attemtps to reuse implementations from ``paste.auth`` for some
of its functionality.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
repoze.xmliter-0.5-2.lbn13.noarch
Wrapper for ``lxml`` trees which serializes to string upon iteration.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
repoze.xmliter-0.6-1.lbn19.noarch
Wrapper for ``lxml`` trees which serializes to string upon iteration.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
repoze.xmliter-0.6-1.lbn25.noarch
Wrapper for ``lxml`` trees which serializes to string upon iteration.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
repoze.zope2-1.0.3-5.lbn13.noarch
repoze.zope2 is a decomposition of the Zope 2 appserver publication
machinery (ZPublisher) into a WSGI application component. It relies
on separately-distributed middleware pieces to perform some of the
features previously handled by ZPublisher and other parts of Zope 2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
repoze.zope2-1.0.3-5.lbn19.noarch
repoze.zope2 is a decomposition of the Zope 2 appserver publication
machinery (ZPublisher) into a WSGI application component. It relies
on separately-distributed middleware pieces to perform some of the
features previously handled by ZPublisher and other parts of Zope 2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
