diff options
| -rw-r--r-- | README.txt | 8 | ||||
| -rw-r--r-- | docs/narr/introduction.rst | 20 |
2 files changed, 11 insertions, 17 deletions
diff --git a/README.txt b/README.txt index f71e64cb5..dc109ff49 100644 --- a/README.txt +++ b/README.txt @@ -1,11 +1,9 @@ repoze.bfg ========== -``repoze.bfg`` is a system for routing web requests to applications -based on graph traversal. It is inspired by Zope's publisher, and -uses Zope libraries to do much of its work. However, it is less -ambitious and less featureful than any released version of Zope's -publisher. +``repoze.bfg`` is a web application framework. It is inspired by +Zope, and uses Zope-related libraries to do much of its work, however +it's simpler than any released version of Zope. Installation ------------ diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst index b4b664cec..bf2e29be1 100644 --- a/docs/narr/introduction.rst +++ b/docs/narr/introduction.rst @@ -2,14 +2,10 @@ ============================== :mod:`repoze.bfg` is a Python web application framework. It is -inspired by Zope's publisher, and uses :term:`Zope` libraries to do -much of its work. However, it is less ambitious and less featureful -than any released version of Zope's publisher. - +inspired by Zope, and uses :term:`Zope` libraries to do much of its +work. However, it simpler than any than any released version of Zope. :mod:`repoze.bfg` uses the :term:`WSGI` protocol to handle requests -and responses, and integrates :term:`Zope`, :term:`Paste`, and -:term:`WebOb` libraries to form the basis for a simple web object -publishing framework. +and responses. Similarities with Other Frameworks ---------------------------------- @@ -104,11 +100,11 @@ to bring new developers up to speed. It's our goal that nothing remain undocumented about :mod:`repoze.bfg`. *Speed*: :mod:`repoze.bfg` is meant to be fast, capable of serving on -the order of 100+ requests per second on today's commodity hardware -for views that do "real work" given proper application implementation. -The *hardware is cheap* mantra has its limits when you're responsible -for managing a great many machines: the fewer you need, the less pain -you'll have. +the order of 100-1000 requests per second on today's commodity +hardware for views that do "real work" given proper application +implementation. The *hardware is cheap* mantra has its limits when +you're responsible for managing a great many machines: the fewer you +need, the less pain you'll have. It's Tested ----------- |