Asynchronous HTTP responses
lvh opened this issue · comments
"Asynchronous" here doesn't mean long polling, HTTP streaming, or even Websockets. It just means "potentially take a long time for an HTTP request to finish". This is related to, but not the same thing as #10: #10 is about representing the same information differently, this about delivering the same representation differently.
This SO answer may be related: https://stackoverflow.com/questions/24549565/using-http-kit-long-polling-with-core-async-channels
We should be using aleph for this.
This is currently fixed in master, with some tests on the way.