Using futures in routes causes issues when doing async write to response stream

[jakobdamjensen]

Long story short. I have routes that does some database lookup with an API based on Futures.

Then problem is, that the lines 102-107 in ehttp.dart makes it impossible to do this since the outputStream is being closed as soon as the inputstream is.

synthReq.inputStream.onClosed = () {
        // Close response stream if needed.
        if (!synthRes.outputStream.closed) {
          synthRes.outputStream.close();
        }
      };

Perhaps I'm doing something wrong.

Removing these lines does make it work but it has a sideeffect in my middlewares.

[jakobdamjensen]

actually the problem is not only in routes but also in middlewares. the fix in the issue does not work for middlewares...

[maiah]

Thanks for this feedback. I haven't worked for a while in this library and I wish to update this soon as I get time. Pull requests are welcome. :)