The primary issue with exposing parts of ts/lib is concern about the C++ ABI breaking on minor and point releases. It may be that with more modern compilers this is less of an issue but we need to either verify that or become much more careful about changes in those files. This problem doesn't arise for libstdc++ because all of it is compiled by the same compiler and version of the compiler. We need to consider if we want to have the same requirement for plugins, which is not currently the case.
On Sat, Sep 16, 2017 at 12:42 AM, Chao Xu <ok...@apache.org> wrote: > Why we don't expose the ts/lib for plugins ? > > I think the ts/lib is an alternative for libstdc++. > > Oknet Xu > > 2017-09-15 22:29 GMT+08:00 Alan Carroll <solidwallofc...@oath.com. > invalid>: > > > Well, my goal has been to, at some point, make all of ink_inet.h > available > > to plugins. This seems a reasonable start. > > > > On Sep 14, 2017 6:09 PM, "Shu Kit Chan" <chanshu...@gmail.com> wrote: > > > > > Here is the PR for this. > > > > > > https://github.com/apache/trafficserver/pull/2520 > > > > > > Thanks. > > > > > > Kit > > > > > > On Wed, Sep 13, 2017 at 2:55 PM, Shu Kit Chan <chanshu...@gmail.com> > > > wrote: > > > > Hi all, > > > > > > > > I would like to see if there is an interest to add a new API to > > > > support parsing IP address into sockaddr. Here is the proposed > > > > signature. > > > > > > > > TSReturnCode TSIpAddrParse(const char *str, size_t str_len, sockaddr > > > *addr) > > > > > > > > This is going to be largely leveraging ats_ip_parse() and > > > > ats_ip_pton() inside ink_inet.h . These are really handy functions > > > > that can parse a string and identify whether it is ipv4 or ipv6 as > > > > well as the port number to put it into the sockaddr struct. > > > > > > > > I can submit the PR soon. > > > > > > > > Thanks. > > > > > > > > Kit > > > > > >
