[jira] [Commented] (TS-2110) Cleanup ts/experimental.h

2014-05-20 Thread Kit Chan (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002866#comment-14002866
 ] 

Kit Chan commented on TS-2110:
--

I will probably take me a while to do the cleanup
Perhaps we should not rush this into the 5.0.0 release

 Cleanup ts/experimental.h
 -

 Key: TS-2110
 URL: https://issues.apache.org/jira/browse/TS-2110
 Project: Traffic Server
  Issue Type: Improvement
  Components: TS API
Reporter: Leif Hedstrom
Assignee: Kit Chan
  Labels: api-change
 Fix For: 5.0.0


 We should go through the APIs in experimental.h, and do one of
 1. Remove
 2. Move to ts/ts.h.in
 3. Leave as is, assuming it's still considered experimental.
 I know there are arguments for and against having an experimental.h include 
 file. I guess I don't have a strong opinion, another solution is to simply 
 keep everything in ts.h.in, but mark APIs that are experimental as such. I do 
 believe having APIs in an experimental state has benefits (such as we can 
 modify such APIs as we see fit, there is no ABI/API compatibility promise).



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (TS-2110) Cleanup ts/experimental.h

2014-05-19 Thread Bryan Call (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14001993#comment-14001993
 ] 

Bryan Call commented on TS-2110:


[~kichan]

Can you get this done in the next week for the 5.0 release?


 Cleanup ts/experimental.h
 -

 Key: TS-2110
 URL: https://issues.apache.org/jira/browse/TS-2110
 Project: Traffic Server
  Issue Type: Improvement
  Components: TS API
Reporter: Leif Hedstrom
Assignee: Kit Chan
  Labels: api-change
 Fix For: 5.0.0


 We should go through the APIs in experimental.h, and do one of
 1. Remove
 2. Move to ts/ts.h.in
 3. Leave as is, assuming it's still considered experimental.
 I know there are arguments for and against having an experimental.h include 
 file. I guess I don't have a strong opinion, another solution is to simply 
 keep everything in ts.h.in, but mark APIs that are experimental as such. I do 
 believe having APIs in an experimental state has benefits (such as we can 
 modify such APIs as we see fit, there is no ABI/API compatibility promise).



--
This message was sent by Atlassian JIRA
(v6.2#6252)