[
https://issues.apache.org/jira/browse/TS-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026960#comment-15026960
]
ASF GitHub Bot commented on TS-4032:
------------------------------------
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/343#issuecomment-159647608
I thought quite a bit about broadcast vs. targeted messages and decided I
prefer this style. It's based on my previous experience with message bus style
mechanisms. The ability to impose additional structure on the messages is very
useful and should be preserved. For instance a plugin might "subscribe" to more
than one channel and use a common library to select messages based on those
subscriptions. If you survey the standard kind of mechanism used for such
message busses you will see this pattern (particularly using domain style names
"a.b.c.d") as very common and I want that to be easy to implement on top of
this mechanism. In terms of overall processing the same work will be done
whether it's the core doing the name comparison or the plugin. I may want to
add some additional support for this so a plugin can easily listen for messages
with a specific prefix.
> Provide command line alert feature for plugins
> ----------------------------------------------
>
> Key: TS-4032
> URL: https://issues.apache.org/jira/browse/TS-4032
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
>
> Add another event to the lifecycle hook, ALERT. This will be sent only from
> an external API, e.g. {{traffic_ctl}}. Any plugin that wants to be alertable
> from the command line can attach to this hook and watch for the event
> {{TS_EVENT_LIFECYCLE_ALERT}}. The data for the event wil be a string that is
> provided by the external agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
