[
https://issues.apache.org/jira/browse/TS-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871652#comment-13871652
]
James Peach commented on TS-2437:
---------------------------------
I think that the right way to do this might be using the lifecycle hooks API.
If you use an observer pattern, you can decouple the API from the code in
iocore. The lifecycle hooks would also let you handle the case where
certificates are reloaded, it's re-entrant and safe for multiple plugins, and
does not require the additional copy of the {{SSL_CTX}} pointers. Take a look
at {{TSLifecycleHookAdd}} and see what you think.
> Add an API to expose SSL_CTX for applications
> ---------------------------------------------
>
> Key: TS-2437
> URL: https://issues.apache.org/jira/browse/TS-2437
> Project: Traffic Server
> Issue Type: Task
> Components: SSL, TS API
> Reporter: Wei Sun
> Assignee: James Peach
> Fix For: 4.2.0
>
> Attachments: TS-2437-2.diff, TS-2437.diff
>
>
> It'll be good to add an API to expose all the SSL_CTXs, so that plugins can
> manipulate their specific ssl settings / call back, etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
