You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/24 03:08:20 UTC
[jira] [Work logged] (TS-1509) Remove TS_PARSE_OK constant
[ https://issues.apache.org/jira/browse/TS-1509?focusedWorklogId=27013&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-27013 ]
ASF GitHub Bot logged work on TS-1509:
--------------------------------------
Author: ASF GitHub Bot
Created on: 24/Aug/16 03:07
Start Date: 24/Aug/16 03:07
Worklog Time Spent: 10m
Work Description: GitHub user bryancall opened a pull request:
https://github.com/apache/trafficserver/pull/910
TS-1509: Remove TS_PARSE_OK constant
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bryancall/trafficserver TS-1509
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/910.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #910
----
commit ac412957fb6069f96c76c2b39ea489030476f15e
Author: Bryan Call <bc...@apache.org>
Date: 2016-08-24T03:06:08Z
TS-1509: Remove TS_PARSE_OK constant
----
Issue Time Tracking
-------------------
Worklog Id: (was: 27013)
Time Spent: 10m
Remaining Estimate: 0h
> Remove TS_PARSE_OK constant
> ---------------------------
>
> Key: TS-1509
> URL: https://issues.apache.org/jira/browse/TS-1509
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: James Peach
> Assignee: Bryan Call
> Priority: Minor
> Labels: api-change, incompatible
> Fix For: 7.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There's TS_PARSE_DONE and TS_PARSE_OK. Which one should a developer handle and what's the difference between?
> Well TS_PARSE_OK is never returned from TSHttpParseResp() so we should just remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)