[jerf]

You don't want to do it because it's hard. If it wasn't hard, you'd do it more. It shouldn't be hard. Our collective reaction to websockets shouldn't be flipping out at how cool they are, it should be "it's about time you gave me back the things you took away".

Of course you want a strong page framework built on top, but the point really is it's easier to start with the streams underneath and build something that limits the streams to the request-response cycle than to go the other way, not that request-response isn't an important simplification that is frequently useful or that it shouldn't be very strong itself.

But you shouldn't go and write it into your WSGI standard or hard-wire your shiny new web server to insist on what are morally CGI pages, and break down crying if somebody wants to stream a little bit.