[Repoze-checkins] r1024 - www/trunk/kiss.repoze.org/content
Chris McDonough
chrism at agendaless.com
Mon May 12 01:45:06 EDT 2008
Author: Chris McDonough <chrism at agendaless.com>
Date: Mon May 12 01:45:06 2008
New Revision: 1024
Log:
Update.
Modified:
www/trunk/kiss.repoze.org/content/repoze_components.stx
Modified: www/trunk/kiss.repoze.org/content/repoze_components.stx
==============================================================================
--- www/trunk/kiss.repoze.org/content/repoze_components.stx (original)
+++ www/trunk/kiss.repoze.org/content/repoze_components.stx Mon May 12 01:45:06 2008
@@ -2,15 +2,15 @@
Repoze Components
- The 'repoze' stack is made up of the following types of software
+ The 'repoze' stack is comprised of the following software
components.
WSGI Applications <a name="applications" />
- - 'repoze.obob'. Status: alpha (0.1)
+ - "repoze.obob":http://svn.repoze.org/repoze.obob/trunk/
- repoze.obob is a stripped-down object publisher that acts as a
- WSGI application. It is responsible for:
+ 'repoze.obob' is a stripped-down object publisher that acts as
+ a WSGI application. It is responsible for:
o selecting the "root" object of the graph for a given request
/ URL;
@@ -33,42 +33,46 @@
the responsibilities of repoze.obob once we get a few "bobs"
done and we see patterns we can move upwards out of the bobs
and back into repoze.obob. The relationship between obob and
- "bob" modules is in flux.
+ "bob" modules is somewhat in flux.
- TODO: do another couple of bobs and figure out what we can
- move upwards.
-
- - 'repoze.zope2'. Status: alpha (0.2)
+ - "repoze.zope2":http://svn.repoze.org/repoze.zope2/trunk/
'repoze.zope2' is a "bob" helper module that implements an
analogue of the Zope 2 ZPublisher, with some major
simplifications and cleanups. Its core mission is to allow
publishing existing Zope2 applications in a WSGI environment
- that externalizes some of the features of "classic" Zope2
- into middleware.
+ that externalizes some of the features of "classic" Zope2 into
+ middleware.
+
+ 'repoze.zope2' is capable of publishing all known Zope
+ applications, including applications which rely on WebDAV and
+ XML-RPC, as well as all known Plone applications.
- Currently, repoze.zope2 is capable of publishing the Zope ZMI
- and CMF applications like Plone which have Zope 3 / Five
- views.
+ - "repoze.plone":http://svn.repoze.org/repoze.plone/trunk/
- It does not yet implement WebDAV or XML-RPC. It expects to do
- virtual hosting by collaborating with the 'repoze.vhm'
- middleware package.
+ 'repoze.plone' is a meta-egg which depends on all Plone
+ component eggs as well as repoze.zope2.
- - 'repoze.zope3'. Status: vapor
+ - "repoze.grok":http://svn.repoze.org/repoze.grok/trunk/
- 'repoze.zope3' is a "bob" helper module that implements an
- analogue of the Zope 3 publication machinery.
+ 'repoze.grok' is a "bob" helper module that implements an
+ analogue of the Zope 3 publication machinery in order to serve
+ up Grok applications.
- - 'repoze.kiss'. Status: alpha (0.1)
+ - "repoze.kiss":http://svn.repoze.org/repoze.kiss/trunk/
'repoze.kiss' is a "bob" module which publishes content
(files, images, templates) from the filesystem, using the
- 'repoze.zope2' helper.
+ 'repoze.zope2' helper. It runs this website.
+
+ - "repoze.mmwsgi":http://svn.repoze.org/repoze.mmwsgi/trunk/
+
+ 'repoze.mmwsgi' is a WSGI wrapper that allows Mailman to be
+ run simply under a WSGI server.
WSGI Middleware <a name="middleware" />
- - 'repoze.tm'. Status: alpha (0.7).
+ - "repoze.tm":http://svn.repoze.org/repoze.tm/trunk/
'repoze.tm' is WSGI middleware that implements a transaction
policy. It uses the 'transaction' module (shipped with ZODB)
@@ -80,7 +84,12 @@
hardcoded in Zope's publisher. 'repoze.tm' is useful in any
web application that requires transactions.
- - 'repoze.retry'. Status: alpha (0.5)
+ A variant of repoze.tm named 'repoze.tm2' is also
+ "available":http://svn.repoze.org/repoze.tm2/trunk/ which does
+ not rely on the entirety of ZODB, but instead relies just on
+ the ZODB 'transaction' module.
+
+ - "repoze.retry":http://svn.repoze.org/repoze.retry/trunk/
'repoze.retry' is WSGI middleware that retries a WSGI request
some configurable number of times if any child application
@@ -91,16 +100,37 @@
TODO: investigate whether any useful RDBMS analogue exists
(e.g., see the 'storm' mailing list).
- - 'repoze.vhm'. Status: alpha (0.2)
+ - "repoze.vhm":http://svn.repoze.org/repoze.vhm/trunk/
'repoze.vhm' is WSGI middleware which normalizes
specially-mangled URLs (or individual header values) into
ordinary paths, with the additional information stored in the
environment for use in generating dynamic URLs. It is an
- analog / replacement for the Zope2 Virtual Host Monster, as
- well as for the Zope3 virtual hosting components.
+ analogue / replacement for the Zope2 Virtual Host Monster.
+
+ - "repoze.errorlog":http://svn.repoze.org/repoze.errorlog/trunk/
- - 'repoze.tempita'. Status: alpha (0.2)
+ 'repoze.errorlog' implements a WSGI middleware filter which
+ intercepts exceptions and writes them to a Python 'logging'
+ module channel (or the 'wsgi.errors' filehandle, if no
+ channel is configured). It also allows the browsing of
+ limited exception history via a browser UI.
+
+ - "repoze.profile":http://svn.repoze.org/repoze.profile/trunk/
+
+ 'repoze.profile' provides a WSGI middleware component which
+ aggregates Python profiling data across all requests to a WSGI
+ application. It provides an HTML UI for viewing profiling
+ data.
+
+ - "repoze.who":http://svn.repoze.org/repoze.who/trunk/
+
+ 'repoze.who' is an identification and authentication framework
+ for arbitrary WSGI applications. It acts as WSGI middleware.
+ It is inspired by Zope 2's Pluggable Authentication Service
+ (PAS) but it is not dependent on Zope in any way.
+
+ - "repoze.tempita":http://svn.repoze.org/repoze.tempita/trunk/
'repoze.tempita' is WSGI middleware egress filter which
conditionally causes the body returned by the application
@@ -108,9 +138,25 @@
templating engine, using replacement values defined within the
'repoze.tempita' Paste middleware configuration.
+ - "repoze.browserid":http://svn.repoze.org/repoze.browserid/trunk/
+
+ 'repoze.browserid' is WSGI middleware loosely based on the
+ Zope 2 concept of "browser ids", which are cookies which
+ represent a browser, for use by sessioning libraries.
+
+ - "repoze.zodbconn":http://svn.repoze.org/repoze.zodbconn/trunk/
+
+ Library which manages ZODB databases and WSGI middleware which
+ makes a ZODB connection available to downstream applications.
+
+ - "repoze.decsec":http://svn.repoze.org/repoze.decsec/trunk/
+
+ Declarative ACL-based security via middleware for WSGI
+ applications. Not widely used.
+
Libraries <a name="libraries" />
- - 'zopelib'. Status: packaged (2.10.4.2).
+ - 'zopelib' (no SVN)
'zopelib' is the entire set of Zope "software home"
'Products'-namespace packages packaged as a
@@ -121,7 +167,7 @@
run from there to repeatably package Zope 2 as an sdist or
bdist.
- - 'cmflib'. Status: packaged (2.1.0.0).
+ - 'cmflib' (no SVN)
'cmflib' is the Zope CMF packaged as a setuptools-compatible
package. It includes all the Zope 'Products'-namespace
@@ -137,12 +183,12 @@
Corporation's SVN
repository":http://svn.zope.org/Sandbox/chrism/eggcmf/
- - 'plonelibs'. Status: packaged (3.0.1.0).
+ - 'plonelibs' (no SVN)
'plonelibs' is a setuptools-compatible repackaging of the
packages that ship in Plone 3's "lib/python" directory.
- - 'ploneproducts'. Status: packaged (3.0.1.0).
+ - 'ploneproducts' (no SVN)
'ploneproducts' is a setuptools-compatible repackaging of the
'Products'-namespace packages that ship in Plone 3.
@@ -150,26 +196,34 @@
It depends on separately released-managed distributions of
Products.PluggableAuthService and Products.PluginRegistry.
- - 'PIL'. Status: packaged (1.1.6)
+ - 'PIL' (no SVN)
'PIL' is a repackaging of the "Python Imaging
Library":http://www.pythonware.com/products/pil/ as a
setuptools-compatible package.
- Future Libraries
+ Buildout-related (zc.buildout recipes and configuration files)
+
+ - Buildouts for
+ "repoze.zope2":http://svn.repoze.org/buildouts/repoze.zope2
+
+ - Buildouts for
+ "repoze.plone":http://svn.repoze.org/buildouts/repoze.plone
+
+ - "repoze.recipe.egg":http://svn.repoze.org/repoze.recipe.egg/trunk
+
+ 'repoze.recipe.egg' is a fork of
+ "zc.recipe.egg":http://pypi.python.org/pypi/zc.recipe.egg , a
+ zc.builout recipe. It does exactly what zc.recipe.egg does,
+ except it also automatically installs scripts from dependent
+ eggs.
+
+ Misc (mostly unsupported "convenience" things)
+
+ - "repoze.django":http://svn.repoze.org/repoze.django/trunk/
+
+ A mechanism to run Django under a Paste server.
- - 'repoze.pas'. Status: vapor
+ - "repoze.trac":http://svn.repoze.org/repoze.trac/trunk/
- 'repoze.pas' is a library which makes the Zope2
- 'PluggableAuthService' product available outside of its
- original ZODB-based target environment. PAS instances can be
- loaded and configured from filesystem-based profiles.
-
- - 'repoze.rommel'. Status: vapor
-
- 'repoze.rommel' factors out the form field marshalling
- traditionally performed by the Zope2 publisher (inside
- 'processInputs'). This feature allows conversion of
- specially-named form fields from strings into other data types
- (e.g., 'foo:int' becomes 'foo', with the value converted to a
- Python 'int').
+ A mechanism to run Trac under a Paste server.
More information about the Repoze-checkins
mailing list