I took a look at the frameworks that you mentioned, none of them use the python3 ioloop by default, though I imagine it might be easy enough to substitute. And compared to the other frameworks on this thread, I don't think I should use minimal to describe aioweb because I've added in and hope to develop more higher level features like session handling, authorization, authentication, configuration and deployment utils. Already using buildout to at a basic level to deploy.
On Monday, January 13, 2014 7:21:53 AM UTC+11, Steven Joseph wrote: > > Hi Amirouche, > > Good question, at this point I don't think aioweb is going to be too > different if you have looked at most of the web frame works that > use async programming style. I hope to make aioweb a framework a very > un-obstructive framework with more replaceable parts, support more > templating style, databases etc. > No there is no WSGI support or websocket support simply because I haven't > gotten around to it yet :). > It'd be great if you could give some critique on the overall design I'm > trying to keep it simple, even better if you could contribute. > > Thanks > > Steven > > On Sunday, January 12, 2014 11:09:49 PM UTC+11, Amirouche Boubekki wrote: >> >> > 2014/1/12 Steven Joseph <[email protected]>: >> >> oops missed out the link 8-| >> >> >> >> https://github.com/jagguli/aioweb >> > >> > >> > There is no documentation? >> > >> > - How does it compare to other async web framework like pulsar, >> > webalchemy, tornado ? >> > - In particular, do you support socket.io or websockets alone? >> > - Does it support WSGI? Why? >> > - How does it compare to non-async web framework django/flask and >> zope-like? >> >> >> It's kind of difficult to compare all this maybe you can answer only >> this question: >> >> - how opinionated aioweb framework is? What makes it unique and relevant? >> >
