Lines Matching full:reference

314 reference-counted mechanism to allow them to be dynamically loaded in and
328 .SS "Reference counting and handles"
329 .IX Subsection "Reference counting and handles"
332 the underlying \s-1ENGINE\s0 object. Ie. one should obtain a new reference when
336 \&\s-1ENGINE\s0 objects have two levels of reference-counting to match the way in
338 inherently a \fBstructural\fR reference \- a structural reference is required
339 to use the pointer value at all, as this kind of reference is a guarantee
340 that the structure can not be deallocated until the reference is released.
342 However, a structural reference provides no guarantee that the \s-1ENGINE\s0 is
347 \&\fBfunctional\fR reference. This kind of reference can be considered a
348 specialised form of structural reference, because each functional reference
349 implicitly contains a structural reference as well \- however to avoid
351 kinds of reference independently. If you have a functional reference to an
354 until after you have released your reference.
358 This basic type of reference is used for instantiating new ENGINEs,
361 reference is sufficient if you only need to query or manipulate the data of
364 The \fBENGINE_new()\fR function returns a structural reference to a new (empty)
370 the last structural reference is released.
373 structural reference will internally obtain another reference \- typically
377 then OpenSSL will have stored a new structural reference internally so the
378 caller is still responsible for freeing their own reference with
380 functions will automatically release the structural reference passed to it
383 \&\s-1ENGINE\s0 list \- they will return a new structural reference to the next (or
385 list, but in either case the structural reference passed to the function is
396 reference can be obtained in one of two ways; from an existing structural
397 reference to the required \s-1ENGINE,\s0 or by asking OpenSSL for the default
400 To obtain a functional reference from an existing structural reference,
405 have allocated a new \fBfunctional\fR reference to the \s-1ENGINE.\s0 All functional
407 implicit structural reference as well).
409 The second way to get a functional reference is by asking OpenSSL for a
430 functional reference to an initialised \s-1ENGINE\s0 whose implementation should be
440 operational. If it returns a functional reference to an \s-1ENGINE,\s0 it will
441 also cache another reference to speed up processing future queries (without
518 \& /* Release the functional reference from ENGINE_init() */
520 \& /* Release the structural reference from ENGINE_by_id() */
610 \&      * ENGINE_init() returned a functional reference, so free the structural
611 \&      * reference from ENGINE_by_id().
641 structural reference. Note that some control commands are defined by OpenSSL