• Nick Craver's avatar
    Sockets: disable NoLinger · ac64b29b
    Nick Craver authored
    This is likely causing some fail as we're not sure everything has been sent. If we *can* be sure, it'd be safe to close it early, otherwise we need to eat the TIME_WAIT.
    
    Buuuuuuut now that I think about it. Linger only works inherently *when there's data left to write*. If our data is *in the pipe* and not yet *in the socket buffer*, we'd be killing it early. This may explain several failures, especially inconsistent and under-load ones.
    
    We really need to figure out how to best close the socket *when the pipe is done* in the Dispose() case. /cc @mgravell
    ac64b29b
Name
Last commit
Last update
..
StackExchange Loading commit data...
StackExchange.Redis.csproj Loading commit data...
build.cmd Loading commit data...