[
https://issues.apache.org/jira/browse/TS-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yunkai Zhang updated TS-2630:
-----------------------------
Description:
The apidefs.h file is used to place common types that can be shared
between internal code and TS APIs.
It's hard to judge what types in api/ts/ts.h should be migrated to
lib/ts/apidefs.h, so this patch is just a beginning ...
Why I named it 'apidefs.h' instead of 'defs.h' and put it into 'lib/ts'?
1) Firstly, there is a 'ink_defs.h' file in 'lib/ts', then 'defs.h' seems
too similar with it. So named it 'apidefs.h' would be more clearly.
2) Since 'apidefs.h' will be shared not only by 'iocore' modules, puting it
into 'lib/ts' would be more suitable than 'iocore/api' or any other else.
was:
ts/types.h file is used to place common types that can be shared between
internal code and TS APIs.
It's hard to judge what types in ts/ts.h should be migrated to ts/types.h, so
this patch is just a beginning ...
> Add ts/types.h to place common types shared between API and core
> ----------------------------------------------------------------
>
> Key: TS-2630
> URL: https://issues.apache.org/jira/browse/TS-2630
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core, TS API
> Reporter: Yunkai Zhang
> Assignee: Yunkai Zhang
> Fix For: 5.0.0
>
>
> The apidefs.h file is used to place common types that can be shared
> between internal code and TS APIs.
> It's hard to judge what types in api/ts/ts.h should be migrated to
> lib/ts/apidefs.h, so this patch is just a beginning ...
> Why I named it 'apidefs.h' instead of 'defs.h' and put it into 'lib/ts'?
> 1) Firstly, there is a 'ink_defs.h' file in 'lib/ts', then 'defs.h' seems
> too similar with it. So named it 'apidefs.h' would be more clearly.
> 2) Since 'apidefs.h' will be shared not only by 'iocore' modules, puting it
> into 'lib/ts' would be more suitable than 'iocore/api' or any other else.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
