Commits

Anonymous committed d5da78a

Updated for 3.1 final

  • Participants
  • Parent commits 50ec0e9

Comments (0)

Files changed (1)

 <div style='float: right; width: 33%; border: 1px solid #990000; background-color: #FFF8F8; margin: 1em; padding: 0;'>
 <h2 style='text-align: center; background-color: #990000; color: white; margin: 0; font: 600 1.5em Verdana, sans-serif; padding: 0.25em;'>N e w s</h2>
     <div style='padding: 1em;'>
+
+
+<div style='background-color: #ffffcc;'> 
+}}}
+==== 2008-06-30 CherryPy 3.1 released ====
+
+On behalf of the CherryPy team, I'm extremely pleased to announce the release of CherryPy 3.1.0 final! The kind of improvements that version 3.0 brought to cherrypy.request, this new version brings to cherrypy.engine: better startup, shutdown, reload, daemonization, signal-handling, scripting, scaffolding, and more. See wiki:WhatsNewIn31 for more details, and read wiki:UpgradeTo31 if you're already using CherryPy.
+{{{ 
+#!html 
+</div> 
 <div style='background-color: #ffffcc;'> 
 }}}
 ==== 2008-05-19 CP3.1rc1 release ====
 
 !CherryPy is a pythonic, object-oriented HTTP framework.
 
-!CherryPy allows developers to build web applications in much the same way they would build any other object-oriented Python program. This usually results in smaller source code developed in less time.
+!CherryPy allows developers to build web applications in much the same way they would build any other object-oriented Python program. This results in smaller source code developed in less time.
 
-!CherryPy is now more than three years old and it is has proven very fast and stable. It is being used in production by many sites, from the simplest ones to the most demanding ones.
+!CherryPy is now more than six years old and it is has proven very fast and stable. It is being used in production by many sites, from the simplest ones to the most demanding ones.
 
 Oh, and most importantly: !CherryPy is '''fun''' to work with :-) Here's how easy it is to write "Hello World" in CherryPy 3:
 
 
  * Your !CherryPy powered web applications are in fact '''stand-alone Python applications embedding their own multi-threaded web server'''. You can deploy them anywhere you can run Python applications. Apache is not required, but it's possible to run a !CherryPy application behind it (or IIS). !CherryPy applications run on Windows, Linux, Mac OS X and any other platform supporting Python.
 
- * You write request handler classes that you tie together in a tree of objects, starting with a root object. !CherryPy maps incoming request URIs to this object tree. The URI '/' represents the 'root' object, '/users/' the 'root.users' object, and so on. Requests are handled by methods inside these request handler classes. GET/POST parameters are passed as standard method parameters; '/users/display?id=123' will call root.users.display(id = '123'). The methods' return strings are then passed back to the browser. You have complete control over which methods are exposed through the web and which ones aren't.
+ * You write request handler classes that you tie together in a tree of objects, starting with a root object. !CherryPy maps incoming request URIs to this object tree. The URI '/' represents the 'root' object, '/users/' the 'root.users' object, and so on. Requests are handled by methods inside these request handler classes. GET/POST parameters are passed as standard method parameters; '/users/display?id=123' will call root.users.display(id = '123'). The methods' return strings are then passed back to the browser. You have complete control over which methods are exposed through the web and which ones aren't. [And if you don't like any of the above, you can swap any part of it out!]
 
  * Beyond this functionality, !CherryPy pretty much stays out of your way. You are free to use any kind of templating, data access etc. technology you want. !CherryPy can also handle sessions, static files, cookies, file uploads and everything you would expect from a decent web framework.
 
 
  * A fast, [http://www.w3.org/Protocols/rfc2616/rfc2616-sec1.html#sec1.2 HTTP/1.1-compliant], [http://www.python.org/dev/peps/pep-0333/ WSGI] thread-pooled webserver
  * Support for any other [http://www.python.org/dev/peps/pep-0333/ WSGI]-enabled webserver or adapter, including Apache, IIS, mod_python, FastCGI, SCGI, and mod_wsgi
- * Easy to run multiple HTTP servers at once
+ * Easy to run multiple HTTP servers (e.g. on multiple ports) at once
  * A powerful [wiki:ConfigAPI configuration system] for developers and deployers alike
  * A flexible [wiki:CustomTools plugin system]
  * Built-in tools for caching, encoding, sessions, authorization, static content, and [wiki:BuiltinTools many more]
 == Versions ==
 
 ||Branch||Status||What's New         ||Upgrading          ||Browse Source||
-||3.1   ||RC    ||[wiki:WhatsNewIn31]||[wiki:UpgradeTo31] ||source:trunk||
+||3.1   ||3.1.0 ||[wiki:WhatsNewIn31]||[wiki:UpgradeTo31] ||source:branches/cherrypy-3.1.x||
 ||3.0   ||3.0.2 ||[wiki:WhatsNewIn30]||[wiki:UpgradeTo30] ||source:branches/cherrypy-3.0.x||
 ||2.2   ||2.2.1 ||[wiki:WhatsNewIn22]||[wiki:UpgradeTo22] ||source:branches/cherrypy-2.x||
 ||2.1   ||2.1.1 ||[wiki:WhatsNewIn21]||                   ||source:branches/cherrypy-2.1||