You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Mladen Turk (JIRA)" <ji...@apache.org> on 2010/05/24 18:52:24 UTC
[jira] Resolved: (TS-333) Remove SocketManager::fast_close
[ https://issues.apache.org/jira/browse/TS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved TS-333.
----------------------------
Assignee: Mladen Turk
Fix Version/s: 2.1.1
Resolution: Fixed
Committed to trunk. Thanks.
> Remove SocketManager::fast_close
> --------------------------------
>
> Key: TS-333
> URL: https://issues.apache.org/jira/browse/TS-333
> Project: Traffic Server
> Issue Type: Improvement
> Components: Network
> Affects Versions: 2.0.0
> Reporter: Alan M. Carroll
> Assignee: Mladen Turk
> Priority: Trivial
> Fix For: 2.1.1
>
> Attachments: ts-333-2-1-0-patch.txt, ts-333-patch-trunk.txt
>
>
> "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 Paul
> Remove SocketManager::fast_close and change all uses to SocketManager::close.
> Remove obsolete argument from SocketManager::close.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.