aspnetcore/test
David Fowler 7854c0604a Remove the events on ConnectionContext (#2023)
- Use the pipe events and removed the Tasks from ConnectionContext
- Remove OnConnectionClosed from FrameConnection. Since the `FrameConnetion` is a single middleware, not the entire pipeline, we shouldn't need to wait on the connection close there.
- It seems like the callbacks are rooted on the pipe even after they fire. This needs to be investigated in pipelines.
2017-08-26 20:19:55 -07:00
..
Kestrel.Core.Tests Remove the events on ConnectionContext (#2023) 2017-08-26 20:19:55 -07:00
Kestrel.FunctionalTests Remove the events on ConnectionContext (#2023) 2017-08-26 20:19:55 -07:00
Kestrel.Tests Use PackageLineup 2017-08-16 14:10:43 -07:00
Kestrel.Transport.Libuv.Tests Remove the events on ConnectionContext (#2023) 2017-08-26 20:19:55 -07:00
shared
Directory.Build.props Use PackageLineup 2017-08-16 14:10:43 -07:00
xunit.runner.json Use PackageLineup 2017-08-16 14:10:43 -07:00