We had a wrapper (the old TS CPP API), and we removed it. Why do we want to
have yet another wrapper now? What's the difference?
Also, I don't like to have libswoc stuff in the API. Using it internally is
ok because we can replace it anytime but having it as part of API is a huge
commitment.
A wr
The atscppapi had problems, but I don't agree that shows any C++ wrapper is
bad. If we say we should not have an alternative C++ API, as well as a C
API, that would imply we should not have a Lua API.
On Wed, Apr 17, 2024 at 2:34 PM Masakazu Kitajo wrote:
> We had a wrapper (the old TS CPP API)
I'm not saying any C++ wrapper should not be made. I just don't think it
should be TS API.
I don't get why we can say the wrapper in a new experimental plugin is good
at this time. We don't have good C++ representation of request, response,
header field, etc. even internally in tscore. And if we h
The atscppapi was deprecated because it was buggy and had bad performance.
On Wed, Apr 17, 2024 at 4:36 PM Masakazu Kitajo wrote:
> I'm not saying any C++ wrapper should not be made. I just don't think it
> should be TS API.
>
> I don't get why we can say the wrapper in a new experimental plugin
