Hello,
Do you mean circuits.web - the web framework?
Please define more specifically what you mean by "middle-ware".
The reason I say this is because of the way circuits.web is
designed (on top of the circuits asynchronous framework)
circuits.web makes no distinction between WSGI Applications,
Middle-ware or Gateways. They are all just "components" that
behave differently and unfortunately there was no clear concept
that could be brought over to circuits.web from WSGI that made
sense for defining "middle-ware behavior".
For example, in my view WSGI Middle-ware means
modifying some part of the request/response as it
is processes through a WSGI Application/Gateway
in some way.
circuits.web achieves this very well by use of the
circuits architecture (components and event handlers)
by allowing you to defining components that allow you
to intercept the request/response and modify it on it's
way through from User to Server and back to User.
I hope this makes sense and if you have further questions
please don't hesitate to ask or come speak to me on
IRC :)
cheers
James