diff options
Diffstat (limited to 'doc/html/boost_asio/overview/core/threads.html')
| -rw-r--r-- | doc/html/boost_asio/overview/core/threads.html | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/html/boost_asio/overview/core/threads.html b/doc/html/boost_asio/overview/core/threads.html index 039d7b0b2d..2faa780947 100644 --- a/doc/html/boost_asio/overview/core/threads.html +++ b/doc/html/boost_asio/overview/core/threads.html @@ -34,7 +34,7 @@ <p> In general, it is safe to make concurrent use of distinct objects, but unsafe to make concurrent use of a single object. However, types such as - <code class="computeroutput"><span class="identifier">io_service</span></code> provide a stronger + <code class="computeroutput"><span class="identifier">io_context</span></code> provide a stronger guarantee that it is safe to use a single object concurrently. </p> <h6> @@ -43,14 +43,14 @@ Pools</a> </h6> <p> - Multiple threads may call <code class="computeroutput"><span class="identifier">io_service</span><span class="special">::</span><span class="identifier">run</span><span class="special">()</span></code> to set up a pool of threads from which + Multiple threads may call <code class="computeroutput"><span class="identifier">io_context</span><span class="special">::</span><span class="identifier">run</span><span class="special">()</span></code> to set up a pool of threads from which completion handlers may be invoked. This approach may also be used with - <code class="computeroutput"><span class="identifier">io_service</span><span class="special">::</span><span class="identifier">post</span><span class="special">()</span></code> - to use a means to perform any computational tasks across a thread pool. + <code class="computeroutput"><span class="identifier">post</span><span class="special">()</span></code> + as a means to perform arbitrary computational tasks across a thread pool. </p> <p> - Note that all threads that have joined an <code class="computeroutput"><span class="identifier">io_service</span></code>'s - pool are considered equivalent, and the <code class="computeroutput"><span class="identifier">io_service</span></code> + Note that all threads that have joined an <code class="computeroutput"><span class="identifier">io_context</span></code>'s + pool are considered equivalent, and the <code class="computeroutput"><span class="identifier">io_context</span></code> may distribute work across them in an arbitrary fashion. </p> <h6> @@ -77,7 +77,7 @@ </p> <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> Asynchronous completion handlers will only be called from threads that - are currently calling <code class="computeroutput"><span class="identifier">io_service</span><span class="special">::</span><span class="identifier">run</span><span class="special">()</span></code>. + are currently calling <code class="computeroutput"><span class="identifier">io_context</span><span class="special">::</span><span class="identifier">run</span><span class="special">()</span></code>. </li></ul></div> <p> Consequently, it is the library user's responsibility to create and manage @@ -88,7 +88,7 @@ </p> <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> - By only calling <code class="computeroutput"><span class="identifier">io_service</span><span class="special">::</span><span class="identifier">run</span><span class="special">()</span></code> from a single thread, the user's + By only calling <code class="computeroutput"><span class="identifier">io_context</span><span class="special">::</span><span class="identifier">run</span><span class="special">()</span></code> from a single thread, the user's code can avoid the development complexity associated with synchronisation. For example, a library user can implement scalable servers that are single-threaded (from the user's point of view). @@ -111,7 +111,7 @@ Also</a> </h6> <p> - <a class="link" href="../../reference/io_service.html" title="io_service">io_service</a>. + <a class="link" href="../../reference/io_context.html" title="io_context">io_context</a>, <a class="link" href="../../reference/post.html" title="post">post</a>. </p> </div> <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr> |