> On Jul 23, 2016, at 4:08 AM, Penkar, Cylus <[email protected]> wrote: > > Thanks James! This exactly what I was looking for! I am going to play with it. > > Making an assumption that the config will be persisted into records.config > right?
I expect so, since there is no distinction between records added by plugins and those added by the core. > > - Cylus > > > > On 7/20/16, 6:40 PM, "James Peach" <[email protected]> wrote: > >> >>> On Jul 21, 2016, at 7:03 AM, Penkar, Cylus <[email protected]> wrote: >>> >>> >>> Folks, >>> >>> I am in a processing for writing a plugin (will talk more about it in the >>> future) and need config to be dynamic. What do we have currently in ATS >>> (and plugins) that I can reuse? >> >> This depends a lot on how you want to configure your plugin. These are the >> main options: >> >> - Add custom records to records.config using APIs like TSMgmtStringCreate() >> and TSMgmtStringGet(). >> - Get notified on configuration events using TSMgmtUpdateRegister(). >> - Remap plugins get automatic reconfiguration support using >> TSRemapNewInstance() and TSRemapDeleteInstance(). >> - Receive a custom configuration message using the plugin message hook, >> TSLifecycleHookAdd(TS_LIFECYCLE_MSG_HOOK). >> - Periodically poll for configuration changes using TSContScheduleEvery(). >> >> J
