Stephen Halter 53ecef0f98 Use libuv to track connections instead of ConcurrentDictionaries ... - This means connections become untracked sooner than before and not all blocks will necessarily be returned. - The assertion in the MemoryPoolBlock2 finalizer was weakened because FilteredStreamAdapter will continue to use blocks after libuv stops tracking the associated connection. - Make 100% sure we don't accept new connections after we dispose the listen socket by using a flag. - Add a (currently unused) AllowStop method to KestrelThread. This is meant to be called from listeners when we stop accepting new connections, but needs investigation to prevent flakiness.		2016-02-17 16:05:35 -08:00
..
Constants.cs	…
Disposable.cs	…
HttpComponentFactory.cs	…
IHttpComponentFactory.cs	…
IKestrelTrace.cs	Close connections as quickly and gracefully as possible on shutdown	2016-02-17 16:05:23 -08:00
ISystemClock.cs	…
IThreadPool.cs	…
KestrelThread.cs	Use libuv to track connections instead of ConcurrentDictionaries	2016-02-17 16:05:35 -08:00
KestrelTrace.cs	Close connections as quickly and gracefully as possible on shutdown	2016-02-17 16:05:23 -08:00
LoggingThreadPool.cs	…
MemoryPool2.cs	Use libuv to track connections instead of ConcurrentDictionaries	2016-02-17 16:05:35 -08:00
MemoryPoolBlock2.cs	Use libuv to track connections instead of ConcurrentDictionaries	2016-02-17 16:05:35 -08:00
MemoryPoolIterator2.cs	…
MemoryPoolIterator2Extensions.cs	…
MemoryPoolSlab2.cs	…
SystemClock.cs	…
TaskUtilities.cs	…