Lines Matching refs:code
55 Application code must create an B<ASYNC_WAIT_CTX> using the ASYNC_WAIT_CTX_new()
61 is closed), application code cleans up with ASYNC_WAIT_CTX_free().
71 application code is typically expected to call this function twice: once to get
86 Implementers of async aware code (e.g. engines) are encouraged to return a
97 Async aware code (e.g. engines) can get the current B<ASYNC_WAIT_CTX> from the
101 code. An existing association with a file descriptor can be obtained using
104 code. This could be any unique value but a good candidate might be the
113 An example of typical usage might be an async capable engine. User code would
116 ASYNC_pause_job() to return control to the user code. The user code can then
119 code that the job should be resumed by making the wait file descriptor
123 As well as a file descriptor, user code may also be notified via a callback. The
131 callback will be called to notify user code when an engine completes a
153 The engine has a fatal problem with this request. The user code should clean up
163 full, so user code should resume the job.
167 ASYNC_WAIT_CTX_get_status() allows user code to obtain the current status value.
168 If the status is any value other than B<ASYNC_STATUS_OK> then the user code
173 code would initiate cryptographic operations, and the engine code would dispatch
175 code would call ASYNC_pause_job() to return control to the user code. After
176 that, user code can perform other tasks. When the hardware completes the
178 user code set a callback by calling ASYNC_WAIT_CTX_set_callback() previously,
