On 25/11/2020 16:46, Christopher Schultz wrote: <snip/>
> Strange that the library is getting a direct reference to the response's > file descriptor. That seems (to me) to be a tactical mistake in an > implementation. Then again, I'm not looking at what is actually being > accomplished, there... it may make perfect sense in context. The library creates a pipe and so gets two file descriptors. It closes the file descriptors so they are returned to the OS's pool of file descriptors. Shortly afterwards the OS reuses one of the file descriptors and assigns it to the socket. So far, so good. Then the library closes the file descriptors for a second time and that closes the socket. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
