SocketManager::close vs. SocketManager::fast_close

["Alan M. Carroll" <am...@network-geographics.com>]

I can't see what the functional difference between these methods is, 
other than close() printing an error message if the caller tries to 
close STDIN (file descriptor 0). Surely that check isn't enough to 
make one "fast" and the other not.

Re: SocketManager::close vs. SocketManager::fast_close

[George Paul <ge...@apache.org>]

There were fast path(s) in the SocketXXX code when used with a kernel
non-native BSD-TCP stack on certain platforms. In the current "cleansed"
code base this is no longer applicable/supported.

-George

On 5/4/10 8:26 AM, Alan M. Carroll wrote:
> I can't see what the functional difference between these methods is, 
> other than close() printing an error message if the caller tries to 
> close STDIN (file descriptor 0). Surely that check isn't enough to 
> make one "fast" and the other not.
>