Lines Matching full:model

5 openssl-quic-concurrency - OpenSSL QUIC Concurrency Model
45 processing model is the same and the application must choose an appropriate
46 concurrency model as discussed below.
59 The B<Single-Threaded Concurrency Model (SCM)>, which supports only
64 The B<Contentive Concurrency Model (CCM)>, which supports multi-threaded usage.
68 The B<Thread-Assisted Concurrency Model (TACM)>, which also supports
80 The B<Single-Threaded Concurrency Model (SCM)> performs no locking or
84 This concurrency model is also useful for an application which wants to use the
89 The B<Contentive Concurrency Model (CCM)> performs automatic locking when making
95 This concurrency model adds the overhead of locking over the Single-Threaded
96 Concurrency Model in order to support multi-threaded usage, but provides limited
102 An advantage of this model relative to the more sophisticated concurrency models
107 The B<Thread-Assisted Concurrency Model (TACM)> is identical to the Contentive
108 Concurrency Model except that a thread is spun up in the background to ensure
118 The default concurrency model is CCM or TACM, depending on the B<SSL_METHOD>
120 concurrency model of CCM, whereas using L<OSSL_QUIC_client_thread_method(3)>
121 results in a default concurrency model of TACM.
136 the chosen concurrency model. If this functionality is disabled, depending on
137 the chosen concurrency model, blocking API calls may not be available and calls
145 available in the Single-Threaded Concurrency Model (SCM), where it works
149 default concurrency model if the application does not explicitly specify a
150 concurrency model or disable it. This is known as Legacy Blocking Compatibility
155 New applications are advised to choose a concurrency model as follows:
163 explicitly select the SCM concurrency model.
169 concurrency model and b) explicitly opt in or out of blocking I/O support
173 An application should select the CCM concurrency model if the application can
177 this, it should select the TACM concurrency model.
181 Applications should explicitly configure a concurrency model during
186 =head1 CONFIGURING A CONCURRENCY MODEL
188 If using an explicit QUIC domain, a concurrency model is chosen when calling
195 Specifying this flag configures the Single-Threaded Concurrency Model (SCM).
199 Speciyfing this flag configures the Contentive Concurrency Model (CCM) (unless
204 Specifying this flag configures the Thread-Assisted Concurrency Model (TACM).
226 The concurrency model for a domain cannot be changed after the domain is
234 concurrency model set on the B<SSL_CTX> is used. This default can be set and get
239 The default concurrency model set on a newly created B<SSL_CTX> is determined as
247 Thread-Assisted Concurrency Model (TACM) is used with the
253 Concurrency Model (SCM) is used, with the B<SSL_DOMAIN_FLAG_LEGACY_BLOCKING>
259 Contentive Concurrency Model (CCM) is used with the
264 Otherwise, the Contentive Concurrency Model (CCM) is used.
268 The default concurrency model may vary between releases of OpenSSL. An
270 consistent usage of a specific concurrency model between releases.
287 If the Thread-Assisted Concurrency Model (TACM) is selected, a background thread
295 Thread-Assisted Concurrency Model.
299 is unspecified under the Thread-Assisted Concurrency Model or when using