[ 
https://issues.apache.org/jira/browse/TS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859475#action_12859475
 ] 

Miles Libbey commented on TS-276:
---------------------------------

[/v2/sdk]$ grep  "InkAPI.h" *
ActionsGuide.html:<pre class="programlisting">#include "InkAPI.h"
ActionsGuide.html:<pre class="programlisting">#include "InkAPI.h"
HTTPHeaders2.html:      <code class="filename">InkAPI.h</code> as <code 
class="code">const char* </code>strings. When
HTTPSessionFunctions.html:<dd><pre class="programlisting">#include InkAPI.h
HTTP_Transactions.html:#include "InkAPI.h"
INKPluginLicenseRequired.html:#include "InkAPI.h"
MIMEHeaders.html:      <code class="filename">InkAPI.h</code> as <code 
class="code"> const char* </code> strings. When
PlusingRegisAndVersionCkg.html:#include "InkAPI.h"
URLs.html:<p>The scheme names above are defined in <code>InkAPI.h</code> as 
<code>const</code> <code>char*</code> strings. When Traffic Server sets the 
scheme portion of the URL (or any

(ie, ActionsGuide has 2 spots that reference InkAPI.h; HTTPHeaders2.html has 1; 
etc)

Looks like you gotten all the remap.h changes

$ grep -i 'INK_SDK_VERSION_5_2' *
INKPluginRegister.html:      <li><code class="code">INK_SDK_VERSION_5_2</code>


looks like you gotten the 'major_ts_version' changes





> Change naming for all include files
> -----------------------------------
>
>                 Key: TS-276
>                 URL: https://issues.apache.org/jira/browse/TS-276
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Diane Smith
>            Assignee: Diane Smith
>             Fix For: 2.1.0
>
>
> Modify names of all include files to reflect recent changes made by Leif.  
> All include files now reside in a new directory, /ts
> For example:
> RemapAPI.h --> remap.h
> InkAPI.h --> ts.h
> Need to follow up to get a more comprehensive list of changes +other aspects 
> of the doc (if any) that could have been affected

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to