Forwarded from cherrypy-users, on the WSGI enhancements therein. ---------- Forwarded message ---------- From: Kevin Dangoor <[EMAIL PROTECTED]> Date: Mar 9, 2006 12:31 PM Subject: [cherrypy-users] Re: Two great posts from Christian To: [EMAIL PROTECTED]
On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I wish knew more, so I can understand how this is an improvement. I > been working with CP for a while now and know what it can do, I just > have no idea how the internal stuff works, rather than I know address > get mapped to objects and callables and stuff. If you guys dont mind > can you explain in simple terms how this is an improvement ?. Pretty > please, i crave to know more.! This is, I think, part of the reason that Ian Bicking has had trouble selling Paste. Describing this stuff to someone who's not doing a web framework has sometimes seemed to be difficult. The next major TurboGears release is entirely based on making good use of WSGI. Here are the real-world benefits: 1) Application composition: imagine that you've written a CherryPy blog and a separate CherryPy wiki. These changes will let you attach both the blog and the wiki to a single site and even do some interesting cross-app integration. 2) Nifty "middleware": a couple months ago, Ian Bicking did a screencast of his "eval exception" package. That package would trap an exception (during development) and let you evaluate expressions on the server side in the context of the exception to help you figure out what went wrong. Very nifty. WSGI middleware is similar to CherryPy filters, but a bit lower level and applied a bit differently. 3) including other apps - as Christian points out, you can toss a MoinMoin into your app if you wish, even though it has nothing to do with CherryPy! You have more ability to build up an entire site in Python without worrying as much about how each part is implemented. 4) code sharing among frameworks - this is the least tangible one for end users, but the results can still be impressive. The middleware is applicable to any web framework that uses WSGI. Each server doesn't *have* to implement their own session handling or caching or exception handling or transaction handling. If a component is designed to work within the WSGI realm, the possibiltiy to reuse it between frameworks is much greater. Ultimately, this should result in better software, because there are more people looking at a single bit of code. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cherrypy-users" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cherrypy-users -~----------~----~----~----~------~----~------~--~--- -- Mike Orr <[EMAIL PROTECTED]> ([EMAIL PROTECTED] address is semi-reliable) _______________________________________________ Quixote-users mailing list [email protected] http://mail.mems-exchange.org/mailman/listinfo/quixote-users
