79 lines
5.8 KiB
HTML
79 lines
5.8 KiB
HTML
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
<title>Requirements on asynchronous socket operations</title>
|
|
<link rel="stylesheet" href="../../boostbook.css" type="text/css">
|
|
<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
|
|
<link rel="home" href="../../index.html" title="Asio">
|
|
<link rel="up" href="../reference.html" title="Reference">
|
|
<link rel="prev" href="synchronous_socket_operations.html" title="Requirements on synchronous socket operations">
|
|
<link rel="next" href="AcceptableProtocol.html" title="Acceptable protocol requirements">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
</head>
|
|
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
|
|
<table cellpadding="2" width="100%"><tr><td valign="top"><img alt="asio C++ library" width="250" height="60" src="../../asio.png"></td></tr></table>
|
|
<hr>
|
|
<div class="spirit-nav">
|
|
<a accesskey="p" href="synchronous_socket_operations.html"><img src="../../prev.png" alt="Prev"></a><a accesskey="u" href="../reference.html"><img src="../../up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../home.png" alt="Home"></a><a accesskey="n" href="AcceptableProtocol.html"><img src="../../next.png" alt="Next"></a>
|
|
</div>
|
|
<div class="section">
|
|
<div class="titlepage"><div><div><h3 class="title">
|
|
<a name="asio.reference.asynchronous_socket_operations"></a><a class="link" href="asynchronous_socket_operations.html" title="Requirements on asynchronous socket operations">Requirements
|
|
on asynchronous socket operations</a>
|
|
</h3></div></div></div>
|
|
<p>
|
|
In this library, <span class="emphasis"><em>asynchronous socket operations</em></span> are
|
|
those member functions having prefix <code class="computeroutput"><span class="identifier">async_</span></code>.
|
|
</p>
|
|
<p>
|
|
For an object <code class="computeroutput"><span class="identifier">s</span></code>, a program
|
|
may initiate asynchronous socket operations such that there are multiple
|
|
simultaneously outstanding asynchronous operations.
|
|
</p>
|
|
<p>
|
|
When there are multiple outstanding asynchronous <a class="link" href="read_write_operations.html" title="Requirements on read and write operations">read
|
|
operations</a> on <code class="computeroutput"><span class="identifier">s</span></code>:
|
|
</p>
|
|
<p>
|
|
— having no argument <code class="computeroutput"><span class="identifier">flags</span></code>
|
|
of type <code class="computeroutput"><span class="identifier">socket_base</span><span class="special">::</span><span class="identifier">message_flags</span></code>, or
|
|
</p>
|
|
<p>
|
|
— having an argument <code class="computeroutput"><span class="identifier">flags</span></code>
|
|
of type <code class="computeroutput"><span class="identifier">socket_base</span><span class="special">::</span><span class="identifier">message_flags</span></code> but where <code class="computeroutput"><span class="special">(</span><span class="identifier">flags</span> <span class="special">&</span> <span class="identifier">socket_base</span><span class="special">::</span><span class="identifier">message_out_of_band</span><span class="special">)</span>
|
|
<span class="special">==</span> <span class="number">0</span></code>
|
|
</p>
|
|
<p>
|
|
then the <code class="computeroutput"><span class="identifier">buffers</span></code> are filled
|
|
in the order in which these operations were issued. The order of invocation
|
|
of the completion handlers for these operations is unspecified.
|
|
</p>
|
|
<p>
|
|
When there are multiple outstanding asynchronous <a class="link" href="read_write_operations.html" title="Requirements on read and write operations">read
|
|
operations</a> on <code class="computeroutput"><span class="identifier">s</span></code> having
|
|
an argument <code class="computeroutput"><span class="identifier">flags</span></code> of type
|
|
<code class="computeroutput"><span class="identifier">socket_base</span><span class="special">::</span><span class="identifier">message_flags</span></code> where <code class="computeroutput"><span class="special">(</span><span class="identifier">flags</span> <span class="special">&</span> <span class="identifier">socket_base</span><span class="special">::</span><span class="identifier">message_out_of_band</span><span class="special">)</span>
|
|
<span class="special">!=</span> <span class="number">0</span></code>
|
|
then the <code class="computeroutput"><span class="identifier">buffers</span></code> are filled
|
|
in the order in which these operations were issued.
|
|
</p>
|
|
<p>
|
|
When there are multiple outstanding asynchronous <a class="link" href="read_write_operations.html" title="Requirements on read and write operations">write
|
|
operations</a> on <code class="computeroutput"><span class="identifier">s</span></code>, the
|
|
<code class="computeroutput"><span class="identifier">buffers</span></code> are transmitted in
|
|
the order in which these operations were issued. The order of invocation
|
|
of the completion handlers for these operations is unspecified.
|
|
</p>
|
|
</div>
|
|
<div class="copyright-footer">Copyright © 2003-2023 Christopher M. Kohlhoff<p>
|
|
Distributed under the Boost Software License, Version 1.0. (See accompanying
|
|
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
|
|
</p>
|
|
</div>
|
|
<hr>
|
|
<div class="spirit-nav">
|
|
<a accesskey="p" href="synchronous_socket_operations.html"><img src="../../prev.png" alt="Prev"></a><a accesskey="u" href="../reference.html"><img src="../../up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../home.png" alt="Home"></a><a accesskey="n" href="AcceptableProtocol.html"><img src="../../next.png" alt="Next"></a>
|
|
</div>
|
|
</body>
|
|
</html>
|