By day time I design and implement connected services and in my offtime I fiddle around with fun OSS things. Trying to help people play with nodeJS and get into programming.
If you're used to NodeJS I'm sure you'll fit in with aiohttp being async and all.
About the generator trick: I haven't tried with gunicorn and multiple processes. I feel like it's going to destroy the performance because each process might be able to serve only on request (the one generating the stream).
Can't wait to read your article on the solution ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Wow thanks for this amazing response! I will take a deeper look at aiohttp. But wrapping my code into a generator would also be a valid fallback.
Maybe I am just too spoiled by the way nodeJS handles streams that I have a hard time understanding why things are so difficult in the python world :)
If you're used to NodeJS I'm sure you'll fit in with aiohttp being async and all.
About the generator trick: I haven't tried with gunicorn and multiple processes. I feel like it's going to destroy the performance because each process might be able to serve only on request (the one generating the stream).
Can't wait to read your article on the solution ;)