1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165 |
- //
- // basic_stream_socket.hpp
- // ~~~~~~~~~~~~~~~~~~~~~~~
- //
- // Copyright (c) 2003-2024 Christopher M. Kohlhoff (chris at kohlhoff dot com)
- //
- // Distributed under the Boost Software License, Version 1.0. (See accompanying
- // file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
- //
- #ifndef BOOST_ASIO_BASIC_STREAM_SOCKET_HPP
- #define BOOST_ASIO_BASIC_STREAM_SOCKET_HPP
- #if defined(_MSC_VER) && (_MSC_VER >= 1200)
- # pragma once
- #endif // defined(_MSC_VER) && (_MSC_VER >= 1200)
- #include <boost/asio/detail/config.hpp>
- #include <cstddef>
- #include <boost/asio/async_result.hpp>
- #include <boost/asio/basic_socket.hpp>
- #include <boost/asio/detail/handler_type_requirements.hpp>
- #include <boost/asio/detail/non_const_lvalue.hpp>
- #include <boost/asio/detail/throw_error.hpp>
- #include <boost/asio/error.hpp>
- #include <boost/asio/detail/push_options.hpp>
- namespace boost {
- namespace asio {
- #if !defined(BOOST_ASIO_BASIC_STREAM_SOCKET_FWD_DECL)
- #define BOOST_ASIO_BASIC_STREAM_SOCKET_FWD_DECL
- // Forward declaration with defaulted arguments.
- template <typename Protocol, typename Executor = any_io_executor>
- class basic_stream_socket;
- #endif // !defined(BOOST_ASIO_BASIC_STREAM_SOCKET_FWD_DECL)
- /// Provides stream-oriented socket functionality.
- /**
- * The basic_stream_socket class template provides asynchronous and blocking
- * stream-oriented socket functionality.
- *
- * @par Thread Safety
- * @e Distinct @e objects: Safe.@n
- * @e Shared @e objects: Unsafe.
- *
- * Synchronous @c send, @c receive, @c connect, and @c shutdown operations are
- * thread safe with respect to each other, if the underlying operating system
- * calls are also thread safe. This means that it is permitted to perform
- * concurrent calls to these synchronous operations on a single socket object.
- * Other synchronous operations, such as @c open or @c close, are not thread
- * safe.
- *
- * @par Concepts:
- * AsyncReadStream, AsyncWriteStream, Stream, SyncReadStream, SyncWriteStream.
- */
- template <typename Protocol, typename Executor>
- class basic_stream_socket
- : public basic_socket<Protocol, Executor>
- {
- private:
- class initiate_async_send;
- class initiate_async_receive;
- public:
- /// The type of the executor associated with the object.
- typedef Executor executor_type;
- /// Rebinds the socket type to another executor.
- template <typename Executor1>
- struct rebind_executor
- {
- /// The socket type when rebound to the specified executor.
- typedef basic_stream_socket<Protocol, Executor1> other;
- };
- /// The native representation of a socket.
- #if defined(GENERATING_DOCUMENTATION)
- typedef implementation_defined native_handle_type;
- #else
- typedef typename basic_socket<Protocol,
- Executor>::native_handle_type native_handle_type;
- #endif
- /// The protocol type.
- typedef Protocol protocol_type;
- /// The endpoint type.
- typedef typename Protocol::endpoint endpoint_type;
- /// Construct a basic_stream_socket without opening it.
- /**
- * This constructor creates a stream socket without opening it. The socket
- * needs to be opened and then connected or accepted before data can be sent
- * or received on it.
- *
- * @param ex The I/O executor that the socket will use, by default, to
- * dispatch handlers for any asynchronous operations performed on the socket.
- */
- explicit basic_stream_socket(const executor_type& ex)
- : basic_socket<Protocol, Executor>(ex)
- {
- }
- /// Construct a basic_stream_socket without opening it.
- /**
- * This constructor creates a stream socket without opening it. The socket
- * needs to be opened and then connected or accepted before data can be sent
- * or received on it.
- *
- * @param context An execution context which provides the I/O executor that
- * the socket will use, by default, to dispatch handlers for any asynchronous
- * operations performed on the socket.
- */
- template <typename ExecutionContext>
- explicit basic_stream_socket(ExecutionContext& context,
- constraint_t<
- is_convertible<ExecutionContext&, execution_context&>::value
- > = 0)
- : basic_socket<Protocol, Executor>(context)
- {
- }
- /// Construct and open a basic_stream_socket.
- /**
- * This constructor creates and opens a stream socket. The socket needs to be
- * connected or accepted before data can be sent or received on it.
- *
- * @param ex The I/O executor that the socket will use, by default, to
- * dispatch handlers for any asynchronous operations performed on the socket.
- *
- * @param protocol An object specifying protocol parameters to be used.
- *
- * @throws boost::system::system_error Thrown on failure.
- */
- basic_stream_socket(const executor_type& ex, const protocol_type& protocol)
- : basic_socket<Protocol, Executor>(ex, protocol)
- {
- }
- /// Construct and open a basic_stream_socket.
- /**
- * This constructor creates and opens a stream socket. The socket needs to be
- * connected or accepted before data can be sent or received on it.
- *
- * @param context An execution context which provides the I/O executor that
- * the socket will use, by default, to dispatch handlers for any asynchronous
- * operations performed on the socket.
- *
- * @param protocol An object specifying protocol parameters to be used.
- *
- * @throws boost::system::system_error Thrown on failure.
- */
- template <typename ExecutionContext>
- basic_stream_socket(ExecutionContext& context, const protocol_type& protocol,
- constraint_t<
- is_convertible<ExecutionContext&, execution_context&>::value,
- defaulted_constraint
- > = defaulted_constraint())
- : basic_socket<Protocol, Executor>(context, protocol)
- {
- }
- /// Construct a basic_stream_socket, opening it and binding it to the given
- /// local endpoint.
- /**
- * This constructor creates a stream socket and automatically opens it bound
- * to the specified endpoint on the local machine. The protocol used is the
- * protocol associated with the given endpoint.
- *
- * @param ex The I/O executor that the socket will use, by default, to
- * dispatch handlers for any asynchronous operations performed on the socket.
- *
- * @param endpoint An endpoint on the local machine to which the stream
- * socket will be bound.
- *
- * @throws boost::system::system_error Thrown on failure.
- */
- basic_stream_socket(const executor_type& ex, const endpoint_type& endpoint)
- : basic_socket<Protocol, Executor>(ex, endpoint)
- {
- }
- /// Construct a basic_stream_socket, opening it and binding it to the given
- /// local endpoint.
- /**
- * This constructor creates a stream socket and automatically opens it bound
- * to the specified endpoint on the local machine. The protocol used is the
- * protocol associated with the given endpoint.
- *
- * @param context An execution context which provides the I/O executor that
- * the socket will use, by default, to dispatch handlers for any asynchronous
- * operations performed on the socket.
- *
- * @param endpoint An endpoint on the local machine to which the stream
- * socket will be bound.
- *
- * @throws boost::system::system_error Thrown on failure.
- */
- template <typename ExecutionContext>
- basic_stream_socket(ExecutionContext& context, const endpoint_type& endpoint,
- constraint_t<
- is_convertible<ExecutionContext&, execution_context&>::value
- > = 0)
- : basic_socket<Protocol, Executor>(context, endpoint)
- {
- }
- /// Construct a basic_stream_socket on an existing native socket.
- /**
- * This constructor creates a stream socket object to hold an existing native
- * socket.
- *
- * @param ex The I/O executor that the socket will use, by default, to
- * dispatch handlers for any asynchronous operations performed on the socket.
- *
- * @param protocol An object specifying protocol parameters to be used.
- *
- * @param native_socket The new underlying socket implementation.
- *
- * @throws boost::system::system_error Thrown on failure.
- */
- basic_stream_socket(const executor_type& ex,
- const protocol_type& protocol, const native_handle_type& native_socket)
- : basic_socket<Protocol, Executor>(ex, protocol, native_socket)
- {
- }
- /// Construct a basic_stream_socket on an existing native socket.
- /**
- * This constructor creates a stream socket object to hold an existing native
- * socket.
- *
- * @param context An execution context which provides the I/O executor that
- * the socket will use, by default, to dispatch handlers for any asynchronous
- * operations performed on the socket.
- *
- * @param protocol An object specifying protocol parameters to be used.
- *
- * @param native_socket The new underlying socket implementation.
- *
- * @throws boost::system::system_error Thrown on failure.
- */
- template <typename ExecutionContext>
- basic_stream_socket(ExecutionContext& context,
- const protocol_type& protocol, const native_handle_type& native_socket,
- constraint_t<
- is_convertible<ExecutionContext&, execution_context&>::value
- > = 0)
- : basic_socket<Protocol, Executor>(context, protocol, native_socket)
- {
- }
- /// Move-construct a basic_stream_socket from another.
- /**
- * This constructor moves a stream socket from one object to another.
- *
- * @param other The other basic_stream_socket object from which the move
- * will occur.
- *
- * @note Following the move, the moved-from object is in the same state as if
- * constructed using the @c basic_stream_socket(const executor_type&)
- * constructor.
- */
- basic_stream_socket(basic_stream_socket&& other) noexcept
- : basic_socket<Protocol, Executor>(std::move(other))
- {
- }
- /// Move-assign a basic_stream_socket from another.
- /**
- * This assignment operator moves a stream socket from one object to another.
- *
- * @param other The other basic_stream_socket object from which the move
- * will occur.
- *
- * @note Following the move, the moved-from object is in the same state as if
- * constructed using the @c basic_stream_socket(const executor_type&)
- * constructor.
- */
- basic_stream_socket& operator=(basic_stream_socket&& other)
- {
- basic_socket<Protocol, Executor>::operator=(std::move(other));
- return *this;
- }
- /// Move-construct a basic_stream_socket from a socket of another protocol
- /// type.
- /**
- * This constructor moves a stream socket from one object to another.
- *
- * @param other The other basic_stream_socket object from which the move
- * will occur.
- *
- * @note Following the move, the moved-from object is in the same state as if
- * constructed using the @c basic_stream_socket(const executor_type&)
- * constructor.
- */
- template <typename Protocol1, typename Executor1>
- basic_stream_socket(basic_stream_socket<Protocol1, Executor1>&& other,
- constraint_t<
- is_convertible<Protocol1, Protocol>::value
- && is_convertible<Executor1, Executor>::value
- > = 0)
- : basic_socket<Protocol, Executor>(std::move(other))
- {
- }
- /// Move-assign a basic_stream_socket from a socket of another protocol type.
- /**
- * This assignment operator moves a stream socket from one object to another.
- *
- * @param other The other basic_stream_socket object from which the move
- * will occur.
- *
- * @note Following the move, the moved-from object is in the same state as if
- * constructed using the @c basic_stream_socket(const executor_type&)
- * constructor.
- */
- template <typename Protocol1, typename Executor1>
- constraint_t<
- is_convertible<Protocol1, Protocol>::value
- && is_convertible<Executor1, Executor>::value,
- basic_stream_socket&
- > operator=(basic_stream_socket<Protocol1, Executor1>&& other)
- {
- basic_socket<Protocol, Executor>::operator=(std::move(other));
- return *this;
- }
- /// Destroys the socket.
- /**
- * This function destroys the socket, cancelling any outstanding asynchronous
- * operations associated with the socket as if by calling @c cancel.
- */
- ~basic_stream_socket()
- {
- }
- /// Send some data on the socket.
- /**
- * This function is used to send data on the stream socket. The function
- * call will block until one or more bytes of the data has been sent
- * successfully, or an until error occurs.
- *
- * @param buffers One or more data buffers to be sent on the socket.
- *
- * @returns The number of bytes sent.
- *
- * @throws boost::system::system_error Thrown on failure.
- *
- * @note The send operation may not transmit all of the data to the peer.
- * Consider using the @ref write function if you need to ensure that all data
- * is written before the blocking operation completes.
- *
- * @par Example
- * To send a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.send(boost::asio::buffer(data, size));
- * @endcode
- * See the @ref buffer documentation for information on sending multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- */
- template <typename ConstBufferSequence>
- std::size_t send(const ConstBufferSequence& buffers)
- {
- boost::system::error_code ec;
- std::size_t s = this->impl_.get_service().send(
- this->impl_.get_implementation(), buffers, 0, ec);
- boost::asio::detail::throw_error(ec, "send");
- return s;
- }
- /// Send some data on the socket.
- /**
- * This function is used to send data on the stream socket. The function
- * call will block until one or more bytes of the data has been sent
- * successfully, or an until error occurs.
- *
- * @param buffers One or more data buffers to be sent on the socket.
- *
- * @param flags Flags specifying how the send call is to be made.
- *
- * @returns The number of bytes sent.
- *
- * @throws boost::system::system_error Thrown on failure.
- *
- * @note The send operation may not transmit all of the data to the peer.
- * Consider using the @ref write function if you need to ensure that all data
- * is written before the blocking operation completes.
- *
- * @par Example
- * To send a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.send(boost::asio::buffer(data, size), 0);
- * @endcode
- * See the @ref buffer documentation for information on sending multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- */
- template <typename ConstBufferSequence>
- std::size_t send(const ConstBufferSequence& buffers,
- socket_base::message_flags flags)
- {
- boost::system::error_code ec;
- std::size_t s = this->impl_.get_service().send(
- this->impl_.get_implementation(), buffers, flags, ec);
- boost::asio::detail::throw_error(ec, "send");
- return s;
- }
- /// Send some data on the socket.
- /**
- * This function is used to send data on the stream socket. The function
- * call will block until one or more bytes of the data has been sent
- * successfully, or an until error occurs.
- *
- * @param buffers One or more data buffers to be sent on the socket.
- *
- * @param flags Flags specifying how the send call is to be made.
- *
- * @param ec Set to indicate what error occurred, if any.
- *
- * @returns The number of bytes sent. Returns 0 if an error occurred.
- *
- * @note The send operation may not transmit all of the data to the peer.
- * Consider using the @ref write function if you need to ensure that all data
- * is written before the blocking operation completes.
- */
- template <typename ConstBufferSequence>
- std::size_t send(const ConstBufferSequence& buffers,
- socket_base::message_flags flags, boost::system::error_code& ec)
- {
- return this->impl_.get_service().send(
- this->impl_.get_implementation(), buffers, flags, ec);
- }
- /// Start an asynchronous send.
- /**
- * This function is used to asynchronously send data on the stream socket.
- * It is an initiating function for an @ref asynchronous_operation, and always
- * returns immediately.
- *
- * @param buffers One or more data buffers to be sent on the socket. Although
- * the buffers object may be copied as necessary, ownership of the underlying
- * memory blocks is retained by the caller, which must guarantee that they
- * remain valid until the completion handler is called.
- *
- * @param token The @ref completion_token that will be used to produce a
- * completion handler, which will be called when the send completes.
- * Potential completion tokens include @ref use_future, @ref use_awaitable,
- * @ref yield_context, or a function object with the correct completion
- * signature. The function signature of the completion handler must be:
- * @code void handler(
- * const boost::system::error_code& error, // Result of operation.
- * std::size_t bytes_transferred // Number of bytes sent.
- * ); @endcode
- * Regardless of whether the asynchronous operation completes immediately or
- * not, the completion handler will not be invoked from within this function.
- * On immediate completion, invocation of the handler will be performed in a
- * manner equivalent to using boost::asio::async_immediate().
- *
- * @par Completion Signature
- * @code void(boost::system::error_code, std::size_t) @endcode
- *
- * @note The send operation may not transmit all of the data to the peer.
- * Consider using the @ref async_write function if you need to ensure that all
- * data is written before the asynchronous operation completes.
- *
- * @par Example
- * To send a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.async_send(boost::asio::buffer(data, size), handler);
- * @endcode
- * See the @ref buffer documentation for information on sending multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- *
- * @par Per-Operation Cancellation
- * On POSIX or Windows operating systems, this asynchronous operation supports
- * cancellation for the following boost::asio::cancellation_type values:
- *
- * @li @c cancellation_type::terminal
- *
- * @li @c cancellation_type::partial
- *
- * @li @c cancellation_type::total
- */
- template <typename ConstBufferSequence,
- BOOST_ASIO_COMPLETION_TOKEN_FOR(void (boost::system::error_code,
- std::size_t)) WriteToken = default_completion_token_t<executor_type>>
- auto async_send(const ConstBufferSequence& buffers,
- WriteToken&& token = default_completion_token_t<executor_type>())
- -> decltype(
- async_initiate<WriteToken,
- void (boost::system::error_code, std::size_t)>(
- declval<initiate_async_send>(), token,
- buffers, socket_base::message_flags(0)))
- {
- return async_initiate<WriteToken,
- void (boost::system::error_code, std::size_t)>(
- initiate_async_send(this), token,
- buffers, socket_base::message_flags(0));
- }
- /// Start an asynchronous send.
- /**
- * This function is used to asynchronously send data on the stream socket.
- * It is an initiating function for an @ref asynchronous_operation, and always
- * returns immediately.
- *
- * @param buffers One or more data buffers to be sent on the socket. Although
- * the buffers object may be copied as necessary, ownership of the underlying
- * memory blocks is retained by the caller, which must guarantee that they
- * remain valid until the completion handler is called.
- *
- * @param flags Flags specifying how the send call is to be made.
- *
- * @param token The @ref completion_token that will be used to produce a
- * completion handler, which will be called when the send completes.
- * Potential completion tokens include @ref use_future, @ref use_awaitable,
- * @ref yield_context, or a function object with the correct completion
- * signature. The function signature of the completion handler must be:
- * @code void handler(
- * const boost::system::error_code& error, // Result of operation.
- * std::size_t bytes_transferred // Number of bytes sent.
- * ); @endcode
- * Regardless of whether the asynchronous operation completes immediately or
- * not, the completion handler will not be invoked from within this function.
- * On immediate completion, invocation of the handler will be performed in a
- * manner equivalent to using boost::asio::async_immediate().
- *
- * @par Completion Signature
- * @code void(boost::system::error_code, std::size_t) @endcode
- *
- * @note The send operation may not transmit all of the data to the peer.
- * Consider using the @ref async_write function if you need to ensure that all
- * data is written before the asynchronous operation completes.
- *
- * @par Example
- * To send a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.async_send(boost::asio::buffer(data, size), 0, handler);
- * @endcode
- * See the @ref buffer documentation for information on sending multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- *
- * @par Per-Operation Cancellation
- * On POSIX or Windows operating systems, this asynchronous operation supports
- * cancellation for the following boost::asio::cancellation_type values:
- *
- * @li @c cancellation_type::terminal
- *
- * @li @c cancellation_type::partial
- *
- * @li @c cancellation_type::total
- */
- template <typename ConstBufferSequence,
- BOOST_ASIO_COMPLETION_TOKEN_FOR(void (boost::system::error_code,
- std::size_t)) WriteToken = default_completion_token_t<executor_type>>
- auto async_send(const ConstBufferSequence& buffers,
- socket_base::message_flags flags,
- WriteToken&& token = default_completion_token_t<executor_type>())
- -> decltype(
- async_initiate<WriteToken,
- void (boost::system::error_code, std::size_t)>(
- declval<initiate_async_send>(), token, buffers, flags))
- {
- return async_initiate<WriteToken,
- void (boost::system::error_code, std::size_t)>(
- initiate_async_send(this), token, buffers, flags);
- }
- /// Receive some data on the socket.
- /**
- * This function is used to receive data on the stream socket. The function
- * call will block until one or more bytes of data has been received
- * successfully, or until an error occurs.
- *
- * @param buffers One or more buffers into which the data will be received.
- *
- * @returns The number of bytes received.
- *
- * @throws boost::system::system_error Thrown on failure. An error code of
- * boost::asio::error::eof indicates that the connection was closed by the
- * peer.
- *
- * @note The receive operation may not receive all of the requested number of
- * bytes. Consider using the @ref read function if you need to ensure that the
- * requested amount of data is read before the blocking operation completes.
- *
- * @par Example
- * To receive into a single data buffer use the @ref buffer function as
- * follows:
- * @code
- * socket.receive(boost::asio::buffer(data, size));
- * @endcode
- * See the @ref buffer documentation for information on receiving into
- * multiple buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- */
- template <typename MutableBufferSequence>
- std::size_t receive(const MutableBufferSequence& buffers)
- {
- boost::system::error_code ec;
- std::size_t s = this->impl_.get_service().receive(
- this->impl_.get_implementation(), buffers, 0, ec);
- boost::asio::detail::throw_error(ec, "receive");
- return s;
- }
- /// Receive some data on the socket.
- /**
- * This function is used to receive data on the stream socket. The function
- * call will block until one or more bytes of data has been received
- * successfully, or until an error occurs.
- *
- * @param buffers One or more buffers into which the data will be received.
- *
- * @param flags Flags specifying how the receive call is to be made.
- *
- * @returns The number of bytes received.
- *
- * @throws boost::system::system_error Thrown on failure. An error code of
- * boost::asio::error::eof indicates that the connection was closed by the
- * peer.
- *
- * @note The receive operation may not receive all of the requested number of
- * bytes. Consider using the @ref read function if you need to ensure that the
- * requested amount of data is read before the blocking operation completes.
- *
- * @par Example
- * To receive into a single data buffer use the @ref buffer function as
- * follows:
- * @code
- * socket.receive(boost::asio::buffer(data, size), 0);
- * @endcode
- * See the @ref buffer documentation for information on receiving into
- * multiple buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- */
- template <typename MutableBufferSequence>
- std::size_t receive(const MutableBufferSequence& buffers,
- socket_base::message_flags flags)
- {
- boost::system::error_code ec;
- std::size_t s = this->impl_.get_service().receive(
- this->impl_.get_implementation(), buffers, flags, ec);
- boost::asio::detail::throw_error(ec, "receive");
- return s;
- }
- /// Receive some data on a connected socket.
- /**
- * This function is used to receive data on the stream socket. The function
- * call will block until one or more bytes of data has been received
- * successfully, or until an error occurs.
- *
- * @param buffers One or more buffers into which the data will be received.
- *
- * @param flags Flags specifying how the receive call is to be made.
- *
- * @param ec Set to indicate what error occurred, if any.
- *
- * @returns The number of bytes received. Returns 0 if an error occurred.
- *
- * @note The receive operation may not receive all of the requested number of
- * bytes. Consider using the @ref read function if you need to ensure that the
- * requested amount of data is read before the blocking operation completes.
- */
- template <typename MutableBufferSequence>
- std::size_t receive(const MutableBufferSequence& buffers,
- socket_base::message_flags flags, boost::system::error_code& ec)
- {
- return this->impl_.get_service().receive(
- this->impl_.get_implementation(), buffers, flags, ec);
- }
- /// Start an asynchronous receive.
- /**
- * This function is used to asynchronously receive data from the stream
- * socket. It is an initiating function for an @ref asynchronous_operation,
- * and always returns immediately.
- *
- * @param buffers One or more buffers into which the data will be received.
- * Although the buffers object may be copied as necessary, ownership of the
- * underlying memory blocks is retained by the caller, which must guarantee
- * that they remain valid until the completion handler is called.
- *
- * @param token The @ref completion_token that will be used to produce a
- * completion handler, which will be called when the receive completes.
- * Potential completion tokens include @ref use_future, @ref use_awaitable,
- * @ref yield_context, or a function object with the correct completion
- * signature. The function signature of the completion handler must be:
- * @code void handler(
- * const boost::system::error_code& error, // Result of operation.
- * std::size_t bytes_transferred // Number of bytes received.
- * ); @endcode
- * Regardless of whether the asynchronous operation completes immediately or
- * not, the completion handler will not be invoked from within this function.
- * On immediate completion, invocation of the handler will be performed in a
- * manner equivalent to using boost::asio::async_immediate().
- *
- * @par Completion Signature
- * @code void(boost::system::error_code, std::size_t) @endcode
- *
- * @note The receive operation may not receive all of the requested number of
- * bytes. Consider using the @ref async_read function if you need to ensure
- * that the requested amount of data is received before the asynchronous
- * operation completes.
- *
- * @par Example
- * To receive into a single data buffer use the @ref buffer function as
- * follows:
- * @code
- * socket.async_receive(boost::asio::buffer(data, size), handler);
- * @endcode
- * See the @ref buffer documentation for information on receiving into
- * multiple buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- *
- * @par Per-Operation Cancellation
- * On POSIX or Windows operating systems, this asynchronous operation supports
- * cancellation for the following boost::asio::cancellation_type values:
- *
- * @li @c cancellation_type::terminal
- *
- * @li @c cancellation_type::partial
- *
- * @li @c cancellation_type::total
- */
- template <typename MutableBufferSequence,
- BOOST_ASIO_COMPLETION_TOKEN_FOR(void (boost::system::error_code,
- std::size_t)) ReadToken = default_completion_token_t<executor_type>>
- auto async_receive(const MutableBufferSequence& buffers,
- ReadToken&& token = default_completion_token_t<executor_type>())
- -> decltype(
- async_initiate<ReadToken,
- void (boost::system::error_code, std::size_t)>(
- declval<initiate_async_receive>(), token,
- buffers, socket_base::message_flags(0)))
- {
- return async_initiate<ReadToken,
- void (boost::system::error_code, std::size_t)>(
- initiate_async_receive(this), token,
- buffers, socket_base::message_flags(0));
- }
- /// Start an asynchronous receive.
- /**
- * This function is used to asynchronously receive data from the stream
- * socket. It is an initiating function for an @ref asynchronous_operation,
- * and always returns immediately.
- *
- * @param buffers One or more buffers into which the data will be received.
- * Although the buffers object may be copied as necessary, ownership of the
- * underlying memory blocks is retained by the caller, which must guarantee
- * that they remain valid until the completion handler is called.
- *
- * @param flags Flags specifying how the receive call is to be made.
- *
- * @param token The @ref completion_token that will be used to produce a
- * completion handler, which will be called when the receive completes.
- * Potential completion tokens include @ref use_future, @ref use_awaitable,
- * @ref yield_context, or a function object with the correct completion
- * signature. The function signature of the completion handler must be:
- * @code void handler(
- * const boost::system::error_code& error, // Result of operation.
- * std::size_t bytes_transferred // Number of bytes received.
- * ); @endcode
- * Regardless of whether the asynchronous operation completes immediately or
- * not, the completion handler will not be invoked from within this function.
- * On immediate completion, invocation of the handler will be performed in a
- * manner equivalent to using boost::asio::async_immediate().
- *
- * @par Completion Signature
- * @code void(boost::system::error_code, std::size_t) @endcode
- *
- * @note The receive operation may not receive all of the requested number of
- * bytes. Consider using the @ref async_read function if you need to ensure
- * that the requested amount of data is received before the asynchronous
- * operation completes.
- *
- * @par Example
- * To receive into a single data buffer use the @ref buffer function as
- * follows:
- * @code
- * socket.async_receive(boost::asio::buffer(data, size), 0, handler);
- * @endcode
- * See the @ref buffer documentation for information on receiving into
- * multiple buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- *
- * @par Per-Operation Cancellation
- * On POSIX or Windows operating systems, this asynchronous operation supports
- * cancellation for the following boost::asio::cancellation_type values:
- *
- * @li @c cancellation_type::terminal
- *
- * @li @c cancellation_type::partial
- *
- * @li @c cancellation_type::total
- */
- template <typename MutableBufferSequence,
- BOOST_ASIO_COMPLETION_TOKEN_FOR(void (boost::system::error_code,
- std::size_t)) ReadToken = default_completion_token_t<executor_type>>
- auto async_receive(const MutableBufferSequence& buffers,
- socket_base::message_flags flags,
- ReadToken&& token = default_completion_token_t<executor_type>())
- -> decltype(
- async_initiate<ReadToken,
- void (boost::system::error_code, std::size_t)>(
- declval<initiate_async_receive>(), token, buffers, flags))
- {
- return async_initiate<ReadToken,
- void (boost::system::error_code, std::size_t)>(
- initiate_async_receive(this), token, buffers, flags);
- }
- /// Write some data to the socket.
- /**
- * This function is used to write data to the stream socket. The function call
- * will block until one or more bytes of the data has been written
- * successfully, or until an error occurs.
- *
- * @param buffers One or more data buffers to be written to the socket.
- *
- * @returns The number of bytes written.
- *
- * @throws boost::system::system_error Thrown on failure. An error code of
- * boost::asio::error::eof indicates that the connection was closed by the
- * peer.
- *
- * @note The write_some operation may not transmit all of the data to the
- * peer. Consider using the @ref write function if you need to ensure that
- * all data is written before the blocking operation completes.
- *
- * @par Example
- * To write a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.write_some(boost::asio::buffer(data, size));
- * @endcode
- * See the @ref buffer documentation for information on writing multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- */
- template <typename ConstBufferSequence>
- std::size_t write_some(const ConstBufferSequence& buffers)
- {
- boost::system::error_code ec;
- std::size_t s = this->impl_.get_service().send(
- this->impl_.get_implementation(), buffers, 0, ec);
- boost::asio::detail::throw_error(ec, "write_some");
- return s;
- }
- /// Write some data to the socket.
- /**
- * This function is used to write data to the stream socket. The function call
- * will block until one or more bytes of the data has been written
- * successfully, or until an error occurs.
- *
- * @param buffers One or more data buffers to be written to the socket.
- *
- * @param ec Set to indicate what error occurred, if any.
- *
- * @returns The number of bytes written. Returns 0 if an error occurred.
- *
- * @note The write_some operation may not transmit all of the data to the
- * peer. Consider using the @ref write function if you need to ensure that
- * all data is written before the blocking operation completes.
- */
- template <typename ConstBufferSequence>
- std::size_t write_some(const ConstBufferSequence& buffers,
- boost::system::error_code& ec)
- {
- return this->impl_.get_service().send(
- this->impl_.get_implementation(), buffers, 0, ec);
- }
- /// Start an asynchronous write.
- /**
- * This function is used to asynchronously write data to the stream socket.
- * It is an initiating function for an @ref asynchronous_operation, and always
- * returns immediately.
- *
- * @param buffers One or more data buffers to be written to the socket.
- * Although the buffers object may be copied as necessary, ownership of the
- * underlying memory blocks is retained by the caller, which must guarantee
- * that they remain valid until the completion handler is called.
- *
- * @param token The @ref completion_token that will be used to produce a
- * completion handler, which will be called when the write completes.
- * Potential completion tokens include @ref use_future, @ref use_awaitable,
- * @ref yield_context, or a function object with the correct completion
- * signature. The function signature of the completion handler must be:
- * @code void handler(
- * const boost::system::error_code& error, // Result of operation.
- * std::size_t bytes_transferred // Number of bytes written.
- * ); @endcode
- * Regardless of whether the asynchronous operation completes immediately or
- * not, the completion handler will not be invoked from within this function.
- * On immediate completion, invocation of the handler will be performed in a
- * manner equivalent to using boost::asio::async_immediate().
- *
- * @par Completion Signature
- * @code void(boost::system::error_code, std::size_t) @endcode
- *
- * @note The write operation may not transmit all of the data to the peer.
- * Consider using the @ref async_write function if you need to ensure that all
- * data is written before the asynchronous operation completes.
- *
- * @par Example
- * To write a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.async_write_some(boost::asio::buffer(data, size), handler);
- * @endcode
- * See the @ref buffer documentation for information on writing multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- *
- * @par Per-Operation Cancellation
- * On POSIX or Windows operating systems, this asynchronous operation supports
- * cancellation for the following boost::asio::cancellation_type values:
- *
- * @li @c cancellation_type::terminal
- *
- * @li @c cancellation_type::partial
- *
- * @li @c cancellation_type::total
- */
- template <typename ConstBufferSequence,
- BOOST_ASIO_COMPLETION_TOKEN_FOR(void (boost::system::error_code,
- std::size_t)) WriteToken = default_completion_token_t<executor_type>>
- auto async_write_some(const ConstBufferSequence& buffers,
- WriteToken&& token = default_completion_token_t<executor_type>())
- -> decltype(
- async_initiate<WriteToken,
- void (boost::system::error_code, std::size_t)>(
- declval<initiate_async_send>(), token,
- buffers, socket_base::message_flags(0)))
- {
- return async_initiate<WriteToken,
- void (boost::system::error_code, std::size_t)>(
- initiate_async_send(this), token,
- buffers, socket_base::message_flags(0));
- }
- /// Read some data from the socket.
- /**
- * This function is used to read data from the stream socket. The function
- * call will block until one or more bytes of data has been read successfully,
- * or until an error occurs.
- *
- * @param buffers One or more buffers into which the data will be read.
- *
- * @returns The number of bytes read.
- *
- * @throws boost::system::system_error Thrown on failure. An error code of
- * boost::asio::error::eof indicates that the connection was closed by the
- * peer.
- *
- * @note The read_some operation may not read all of the requested number of
- * bytes. Consider using the @ref read function if you need to ensure that
- * the requested amount of data is read before the blocking operation
- * completes.
- *
- * @par Example
- * To read into a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.read_some(boost::asio::buffer(data, size));
- * @endcode
- * See the @ref buffer documentation for information on reading into multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- */
- template <typename MutableBufferSequence>
- std::size_t read_some(const MutableBufferSequence& buffers)
- {
- boost::system::error_code ec;
- std::size_t s = this->impl_.get_service().receive(
- this->impl_.get_implementation(), buffers, 0, ec);
- boost::asio::detail::throw_error(ec, "read_some");
- return s;
- }
- /// Read some data from the socket.
- /**
- * This function is used to read data from the stream socket. The function
- * call will block until one or more bytes of data has been read successfully,
- * or until an error occurs.
- *
- * @param buffers One or more buffers into which the data will be read.
- *
- * @param ec Set to indicate what error occurred, if any.
- *
- * @returns The number of bytes read. Returns 0 if an error occurred.
- *
- * @note The read_some operation may not read all of the requested number of
- * bytes. Consider using the @ref read function if you need to ensure that
- * the requested amount of data is read before the blocking operation
- * completes.
- */
- template <typename MutableBufferSequence>
- std::size_t read_some(const MutableBufferSequence& buffers,
- boost::system::error_code& ec)
- {
- return this->impl_.get_service().receive(
- this->impl_.get_implementation(), buffers, 0, ec);
- }
- /// Start an asynchronous read.
- /**
- * This function is used to asynchronously read data from the stream socket.
- * socket. It is an initiating function for an @ref asynchronous_operation,
- * and always returns immediately.
- *
- * @param buffers One or more buffers into which the data will be read.
- * Although the buffers object may be copied as necessary, ownership of the
- * underlying memory blocks is retained by the caller, which must guarantee
- * that they remain valid until the completion handler is called.
- *
- * @param token The @ref completion_token that will be used to produce a
- * completion handler, which will be called when the read completes.
- * Potential completion tokens include @ref use_future, @ref use_awaitable,
- * @ref yield_context, or a function object with the correct completion
- * signature. The function signature of the completion handler must be:
- * @code void handler(
- * const boost::system::error_code& error, // Result of operation.
- * std::size_t bytes_transferred // Number of bytes read.
- * ); @endcode
- * Regardless of whether the asynchronous operation completes immediately or
- * not, the completion handler will not be invoked from within this function.
- * On immediate completion, invocation of the handler will be performed in a
- * manner equivalent to using boost::asio::async_immediate().
- *
- * @par Completion Signature
- * @code void(boost::system::error_code, std::size_t) @endcode
- *
- * @note The read operation may not read all of the requested number of bytes.
- * Consider using the @ref async_read function if you need to ensure that the
- * requested amount of data is read before the asynchronous operation
- * completes.
- *
- * @par Example
- * To read into a single data buffer use the @ref buffer function as follows:
- * @code
- * socket.async_read_some(boost::asio::buffer(data, size), handler);
- * @endcode
- * See the @ref buffer documentation for information on reading into multiple
- * buffers in one go, and how to use it with arrays, boost::array or
- * std::vector.
- *
- * @par Per-Operation Cancellation
- * On POSIX or Windows operating systems, this asynchronous operation supports
- * cancellation for the following boost::asio::cancellation_type values:
- *
- * @li @c cancellation_type::terminal
- *
- * @li @c cancellation_type::partial
- *
- * @li @c cancellation_type::total
- */
- template <typename MutableBufferSequence,
- BOOST_ASIO_COMPLETION_TOKEN_FOR(void (boost::system::error_code,
- std::size_t)) ReadToken = default_completion_token_t<executor_type>>
- auto async_read_some(const MutableBufferSequence& buffers,
- ReadToken&& token = default_completion_token_t<executor_type>())
- -> decltype(
- async_initiate<ReadToken,
- void (boost::system::error_code, std::size_t)>(
- declval<initiate_async_receive>(), token,
- buffers, socket_base::message_flags(0)))
- {
- return async_initiate<ReadToken,
- void (boost::system::error_code, std::size_t)>(
- initiate_async_receive(this), token,
- buffers, socket_base::message_flags(0));
- }
- private:
- // Disallow copying and assignment.
- basic_stream_socket(const basic_stream_socket&) = delete;
- basic_stream_socket& operator=(const basic_stream_socket&) = delete;
- class initiate_async_send
- {
- public:
- typedef Executor executor_type;
- explicit initiate_async_send(basic_stream_socket* self)
- : self_(self)
- {
- }
- const executor_type& get_executor() const noexcept
- {
- return self_->get_executor();
- }
- template <typename WriteHandler, typename ConstBufferSequence>
- void operator()(WriteHandler&& handler,
- const ConstBufferSequence& buffers,
- socket_base::message_flags flags) const
- {
- // If you get an error on the following line it means that your handler
- // does not meet the documented type requirements for a WriteHandler.
- BOOST_ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
- detail::non_const_lvalue<WriteHandler> handler2(handler);
- self_->impl_.get_service().async_send(
- self_->impl_.get_implementation(), buffers, flags,
- handler2.value, self_->impl_.get_executor());
- }
- private:
- basic_stream_socket* self_;
- };
- class initiate_async_receive
- {
- public:
- typedef Executor executor_type;
- explicit initiate_async_receive(basic_stream_socket* self)
- : self_(self)
- {
- }
- const executor_type& get_executor() const noexcept
- {
- return self_->get_executor();
- }
- template <typename ReadHandler, typename MutableBufferSequence>
- void operator()(ReadHandler&& handler,
- const MutableBufferSequence& buffers,
- socket_base::message_flags flags) const
- {
- // If you get an error on the following line it means that your handler
- // does not meet the documented type requirements for a ReadHandler.
- BOOST_ASIO_READ_HANDLER_CHECK(ReadHandler, handler) type_check;
- detail::non_const_lvalue<ReadHandler> handler2(handler);
- self_->impl_.get_service().async_receive(
- self_->impl_.get_implementation(), buffers, flags,
- handler2.value, self_->impl_.get_executor());
- }
- private:
- basic_stream_socket* self_;
- };
- };
- } // namespace asio
- } // namespace boost
- #include <boost/asio/detail/pop_options.hpp>
- #endif // BOOST_ASIO_BASIC_STREAM_SOCKET_HPP
|