Well, in the intro I described, that I looked at the bunch of microframeworks, but dismissed them, because there was no way they would run with the heap size available on PyBoard. Instead, I decided to write one from scratch, to keep it unbloated, and to ultimately be able to run it on MCU-level environment. That said, my primary development and usage platform is Unix port of MicroPython. So, whoever interested to run it on MCU board, would need to contribute to the project. And of course, that requires some kind of TCP/IP connectivity - ideally, BSD sockets API (including non-blocking mode), though any other sensible API should be easy to integrate either.
Currently, a trivial webapp can be run in 64K of heap. I have to say, that's much more than I expected (compare that with similar confession in http://forum.micropython.org/viewtopic. ... t=154#p651
). For comparison, simple single-threaded server from examples/unix/ can run in 10K (which is, as you may expect, is more than I expected either