On 11/16/05, Ian Bicking <[EMAIL PROTECTED]> wrote: > > Jonathan LaCour wrote: > > This got me thinking that maybe filters are the wrong approach, as are > > decorators. Why not make both the transaction-per-request and > > automated-error-handling WSGI middleware? I am not an expert on the > > WSGI specification, but it seems at a cursory glance to be possible, > > and then we wouldn't have to convince CherryPy to change anything. > > I'm not sure what the status is of WSGI middleware and CherryPy, and how > easy they are to put together. Mostly in terms of configuring a stack > of middleware. But anyway, I posted a kind of scarecrow implementation > of this a while back: > http://blog.ianbicking.org/more-perfect-app-server-wsgi-transactions.html > > Also, exceptions have to be raised all the way to this middleware for > the system to work.
Yes, I have a feeling that this would not be the easiest path to implementation, for both of these reasons. I think the decorator path is likely the easiest, *and* it potentially allows someone to specify that no transaction is required for a given method. Kevin
