Ticket #700 (task)

After re-reading the linked thread, I do realize that the wsgiapp tool is slightly misleading if you're not fluent with the limits between WSGI and CP. It would certainly make things easier to explain and document by deprecating it.

I think people who use it will find easy workarounds anyway.

I might as well be explicit about the limits: the wsgiapp tool doesn't follow the WSGI spec, which says "a middleware component must yield at least one value each time its underlying application yields a value." Instead, the wsgiapp tool collects and collapses the response from the next application.

That can't really be worked around without turning the CP core inside-out again, or putting horrible limits on what WSGI components you can hook up to it.

However, the tool is instructive, and useful in some environments. I'd be happy moving it to a page on the tools wiki (with lots of documentation about the limitations).

Fixed in [1763].