[
https://issues.apache.org/jira/browse/TS-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027120#comment-15027120
]
ASF GitHub Bot commented on TS-4032:
------------------------------------
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/343#issuecomment-159670541
That seems fine, but this mechanism doesn't provide channels or any ability
for plugins to subscribe to messages. There's no reason to think that all
plugins will implement the same protocol on top of this mechanism, so
preserving the ability to send messages to specific plugins still seems
appropriate.
It sounds like you have a particular message format in mind. Could you
clarify that?
> 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)
