You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/05/07 23:15:00 UTC
[jira] [Commented] (TS-3569) Replace UNSAFE_FORCE_MUTEX with an
sdk_assert, and relax mutex requirements on Schedule()
[ https://issues.apache.org/jira/browse/TS-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533390#comment-14533390 ]
Leif Hedstrom commented on TS-3569:
-----------------------------------
As a side effect, I'm relaxing (as per [~jpeach@apache.org]'s suggestion) the requirement for a mutex / lock on the TSSchedule*() APIs. It passes the regressions, so what could possibly go wrong.
> Replace UNSAFE_FORCE_MUTEX with an sdk_assert, and relax mutex requirements on Schedule()
> -----------------------------------------------------------------------------------------
>
> Key: TS-3569
> URL: https://issues.apache.org/jira/browse/TS-3569
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 6.0.0
>
>
> I'm not sure when we'd want to change any of this behavior, it seems the big ugly mutex is just that, ugly. Maybe it's time to just clean this up?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)