Re: SSL Session Plugin API proposal

2015-06-12 Thread Susan Hinrichs
Updated the pull request. On 6/11/2015 1:57 PM, Susan Hinrichs wrote: Replies inline On 6/11/2015 12:28 PM, James Peach wrote: On Jun 11, 2015, at 8:09 AM, Susan Hinrichs wrote: James, thanks for the comments. I had some old references and as you noted did not discuss how memory is tracke

Re: SSL Session Plugin API proposal

2015-06-11 Thread Susan Hinrichs
Replies inline On 6/11/2015 12:28 PM, James Peach wrote: On Jun 11, 2015, at 8:09 AM, Susan Hinrichs wrote: James, thanks for the comments. I had some old references and as you noted did not discuss how memory is tracked through the API's. Thanks Susan. I actually find it pretty difficult

Re: SSL Session Plugin API proposal

2015-06-11 Thread James Peach
> On Jun 11, 2015, at 8:09 AM, Susan Hinrichs > wrote: > > James, thanks for the comments. I had some old references and as you noted > did not discuss how memory is tracked through the API's. Thanks Susan. I actually find it pretty difficult to review API changes from documentation. It wou

Re: SSL Session Plugin API proposal

2015-06-11 Thread Susan Hinrichs
James, thanks for the comments. I had some old references and as you noted did not discuss how memory is tracked through the API's. I've updated the document http://network-geographics.com/ats/docs/ssl-session-api.en.html On my branch, I have a very simple example plugin which exercises the

Re: SSL Session Plugin API proposal

2015-06-10 Thread James Peach
> On Jun 10, 2015, at 3:24 PM, Susan Hinrichs > wrote: > > I haven't heard anything about this. We did discuss it at the Austin Summit. > There was general agreement to the idea. I've updated the document to > reflect what I have implemented. I will create a pull request with the code >

Re: SSL Session Plugin API proposal

2015-06-10 Thread Susan Hinrichs
I haven't heard anything about this. We did discuss it at the Austin Summit. There was general agreement to the idea. I've updated the document to reflect what I have implemented. I will create a pull request with the code changes later this evening. The details of the API are at http://ne