Ah, I see. Many thanks for the explanation.
Sunjeet
On 2012-04-05, at 7:36 AM, Jakob Bohm wrote:
> On 4/5/2012 5:36 AM, Sunjeet Singh wrote:
>>> ENGINE_free all of the structural references you got, including the one
>>> for the ENGINE you're using
>> And so in order to free all structural r
On 4/5/2012 5:36 AM, Sunjeet Singh wrote:
ENGINE_free all of the structural references you got, including the one for
the ENGINE you're using
And so in order to free all structural references of an ENGINE * e, I could
just do this?-
while( e->struct_ref> 0 ) {
ENGINE_free( e );
}
> ENGINE_free all of the structural references you got, including the one for
> the ENGINE you're using
And so in order to free all structural references of an ENGINE * e, I could
just do this?-
while( e->struct_ref > 0 ) {
ENGINE_free( e );
}
And to keep all but one functional refer
On 4 Apr 2012, at 12:10 PM, Sunjeet Singh wrote:
> If I have multiple SSL connections using an engine at the same time, IS IT
> TRUE THAT-
> 1. I should have at least one structural and one functional reference for the
> entire duration within which the engine will be used i.e., between the call
Hi,
I'm working on an OpenSSL Engine implementation and I don't entirely get the
idea behind Structural and Functional references. So, I'd be very grateful if
someone could comment on my approach of handling references.
If I have multiple SSL connections using an engine at the same time, IS IT
