mlavin/aiodjango

Experiment Mixing Django with aiohttp

aiodjango's Issues

Customization of the App

Need to expose ways to customize/extend the aiohttp.web application which is created such as with additional middleware.

Convert URL Regexs

aiohttp.web does have a default regex router and the current solution is a bit of a hack. It's unlikely to work for more complex cases.

Static Files

Might what to make the static files automatically served by the async server. Something like whitenoise built-in. Not sure if sendfile works with aiohttp.

Test Utilities

Probably need to create utilities like the liveserver/test client for testing these additional views.

Auth Access

Like sessions, the coroutine views will also likely want to know about the current user.

WSGI Access to App/Loop

The WSGI app may want access to the event loop and/or the aio app.

Clean Up Access Log in Runserver

It's currently a unreadable mess. Nice to get a format closer to the original format. Color would be a nice to have but not really needed.

Tests

Not a lot of code in this project yet but still needs to be tested.

Benchmarking

The WSGI app shouldn't block the IO loop since it runs in a executor but it would be good to benchmark and test various scenarios such as DB access and generally slow views.

Full Documentation

The README is nice but if this is ever going to be more than a proof of concept it needs proper docs.

Configure Executor

Probably need a way to configure the executor used to run the WSGI app (CPU vs Theads or # of threads).

Python Packaging

Needed if want to test outside of the demo application.

Live Demo

A fully deployed live demo would be nice for both the demo and to monitor usage/performance.

Session Access

Coroutine views will likely want access to the session and that should be available by default.