Andrew Svetlov

I think request handler should return dict instance. The instance should be converted into binary data by some processor (you can call it serializer or renderer). Processor should support template...

No, I don't like to return processor name from handler. My vision is closer to: ``` @renderer(template='page.jinja2') def handler(request): return {'foo': 'bar'} ```

Would you provide a patch which fixes aioes, without yarl monkeypatching?

The second one

Hi. I doubt that rivers should be part of aioes. elasticsearch-py has no river api. API is not well-structured. There is `/_river/{river_name}/_meta`, meta format is river-specific. From my perspective better...

@kxepal feel free to make third-party library on top of aioes. You really need only for Elasticsearch.transport for accessing to river API.

@hellysmile have you a chance to take a look?

Support for custom proxies is in my todo list. There is no estimation yet.

Thanks for the report. I have a plan for working on it; I hope the fix will be a part of aiohttp 3.8

Interesting idea, thanks!