On 12.10.2006 13:26, Mladen Turk wrote: > Ruediger Pluem wrote: > >> >> But yes, in theory their remains a race here if the proxy reuses the >> connection >> faster then the backend needs time to close the socket after sending >> the response. >> > > Does the problem exists with the current trunk as well? > The way how trunk detects the closed backend has changed > by not using read any more.
Yes, because of a race condition. The remote side could close the connection just after the check happened. The closing could even happen while the first data is on its way to the backend. So the first write(s) can succeed, because the FIN from the backend is on its way during this time. Nevertheless it is very good to have a reliable socket connection check (as on trunk) as this reduces the number of cases where this happens a lot and makes handling of such cases a lot easier. Regards Rüdiger
