Re: [API] Administrative JSON-RPC interface

I'm very interested in having a much more open control plane. On Wed, Apr 8, 2020 at 12:52 PM Alan Carroll wrote: > We (Damian and I) are starting work on replacing the current administrative > control channel with an JSON-RPC based one, as I have mentioned at previous > summits. The basic

Re: Thread affinity on Continuations vs TSContSchedule API

Something I find challenging about TSContScheduleOnPool and others is that there is no much documentation about good practices to configure thread pools. For example the only documentation I found about task threads only says that you must have at least 1 task thread:

Re: [API Proposal] Extend CPPAPI RemapPlugin to access TSRemapRequestInfo

David Calavera wrote: > Hi all, > > This is a proposal to add a new virtual method to the CPP API to get > access to TSRemapRequestInfo. > > We're working on a plugin that changes the origin URL on demand, and the > CPP API is a little bit confusing around which U

Re: [VOTE] Release Apache Traffic Server 7.1.9 (RC2)

+1 On Wed, Feb 26, 2020 at 1:54 PM Bryan Call wrote: > I've prepared a release candidate (rc2) for 7.1.9. The release notes for > 7.1.9 are available at: > > > https://github.com/apache/trafficserver/pulls?utf8=✓=is%3Aclosed+is%3Apr+milestone%3A7.1.9 >

Re: Proposal for 9.x: Support external log rotation via a handled signal

Great idea. +1 On Fri, Jan 24, 2020 at 10:06 AM Steven R. Feltner wrote: > > +1 > > On 1/24/20, 10:43 AM, "Leif Hedstrom" wrote: > > > On Jan 24, 2020, at 10:06 AM, Bryan Call wrote: > > > > +1 - supports the UNIX Philosophy of having each program do one > thing well > > +1.

Async providers and std::future

Hi all, I was exprimenting with a new plugin over the weekend with and arrived to a blocking point, probably because my lack of experience with the async story in C++. This is the challenge. I'm integrating a C++ client that invokes calls asynchronously and returns objects that implement

[PROPOSAL] Make atscppapi::RegisterGlobalPlugin return a value

I noticed that atscppapi::RegisterGlobalPlugin doesn't return any value. This makes impossible for plugins that use to to know whether they need to abort initialization or continue after registering the plugin. I'm proposing to change the method signature to return a boolean value, so plugins can

Re: ATS Cache Analysis Tool

I'm very interested in using this tool. We were thinking about writing something very similar. Cheers, David On Wed, Apr 4, 2018 at 8:57 AM, Bryan Call wrote: > I would suggest creating a pull request and add it to the tools directory > for ATS: > >

Re: [VOTE] Release Apache Traffic Server 7.1.1 (RC1)

+1 to this release. It solves the problems we found with SNI plugins in the 7.1.0 version. We're actually running this in production since last week and we haven't found any issue yet. Cheers, David On Tue, Sep 5, 2017 at 10:43 AM, Steven R. Feltner wrote: > I have

Re: Add TSSslContextCreate and TSSslContextDestroy to the API

Hi everyone! Is there anything else I can do to move this forward? Cheers, David On Mon, Apr 25, 2016 at 9:22 AM, David Calavera <david.calav...@gmail.com> wrote: > I've renamed the function as part of my pull request. You can see the > change in this commit: > > > http

Re: Add TSSslContextCreate and TSSslContextDestroy to the API

I've renamed the function as part of my pull request. You can see the change in this commit: https://github.com/apache/trafficserver/pull/594/commits/4fc12c4b2d9bf7ab11b84006cf1be6657868632a Cheers, David On Sun, Apr 24, 2016 at 3:15 PM, David Calavera <david.calav...@gmail.com>

Re: Add TSSslContextCreate and TSSslContextDestroy to the API

use, so the pull request > > includes > > a corresponding TSSslContextDestroy API function for freeing the context > > (just > > wraps the open ssl call for this, but having an API function makes it > more > > obvious > > that it's up to the plugin author to f

Add TSSslContextCreate and TSSslContextDestroy to the API

Originally proposed in https://github.com/apache/trafficserver/pull/402. It would be convenient to have those two methods in the API to properly create SSL contexts setting the right configuration from records.config. I opened a ticket to track the issue: