Lines Matching full:reference

238 reference-counted mechanism to allow them to be dynamically loaded in and
252 .SS "Reference counting and handles"
253 .IX Subsection "Reference counting and handles"
256 the underlying ENGINE object. Ie. one should obtain a new reference when
260 ENGINE objects have two levels of reference-counting to match the way in
262 inherently a \fBstructural\fR reference \- a structural reference is required
263 to use the pointer value at all, as this kind of reference is a guarantee
264 that the structure can not be deallocated until the reference is released.
266 However, a structural reference provides no guarantee that the ENGINE is
271 \&\fBfunctional\fR reference. This kind of reference can be considered a
272 specialised form of structural reference, because each functional reference
273 implicitly contains a structural reference as well \- however to avoid
275 kinds of reference independently. If you have a functional reference to an
278 until after you have released your reference.
282 This basic type of reference is used for instantiating new ENGINEs,
285 reference is sufficient if you only need to query or manipulate the data of
288 The \fBENGINE_new()\fR function returns a structural reference to a new (empty)
294 the last structural reference is released. If the argument to \fBENGINE_free()\fR
298 structural reference will internally obtain another reference \- typically
302 then OpenSSL will have stored a new structural reference internally so the
303 caller is still responsible for freeing their own reference with
305 functions will automatically release the structural reference passed to it
308 ENGINE list \- they will return a new structural reference to the next (or
310 list, but in either case the structural reference passed to the function is
321 reference can be obtained in one of two ways; from an existing structural
322 reference to the required ENGINE, or by asking OpenSSL for the default
325 To obtain a functional reference from an existing structural reference,
330 have allocated a new \fBfunctional\fR reference to the ENGINE. All functional
332 implicit structural reference as well).
334 The second way to get a functional reference is by asking OpenSSL for a
355 functional reference to an initialised ENGINE whose implementation should be
365 operational. If it returns a functional reference to an ENGINE, it will
366 also cache another reference to speed up processing future queries (without
443 \& /* Release the functional reference from ENGINE_init() */
445 \& /* Release the structural reference from ENGINE_by_id() */
535 \&      * ENGINE_init() returned a functional reference, so free the structural
536 \&      * reference from ENGINE_by_id().
566 structural reference. Note that some control commands are defined by OpenSSL