body_read_stream implementation - WORK IN PROGRESS

include/boost/beast2/body_read_stream.hpp

@@ -0,0 +1,239 @@
+//
+// Copyright (c) 2016-2019 Vinnie Falco (vinnie dot falco at gmail 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)
+//
+// Official repository: https://github.com/vinniefalco/http_io
+//
+
+#ifndef BOOST_HTTP_IO_BODY_READ_STREAM_HPP
+#define BOOST_HTTP_IO_BODY_READ_STREAM_HPP
+
+#include <boost/beast2/detail/config.hpp>
+#include <boost/http_proto/parser.hpp>
+#include <boost/asio/async_result.hpp>
+#include <boost/system/error_code.hpp>
+
+namespace boost {
+namespace beast2 {
+
+    /** A body reader for HTTP/1 messages.
+
+        This type meets the requirements of asio's
+        AsyncReadStream, and is constructed with a reference to an
+        underlying AsyncReadStream.
+
+        Any call to `async_read_some` initially triggers reads
+        from the underlying stream until all of the HTTP headers
+        have been read and processed. Thereafter, each subsequent
+        call to `async_read_some` triggers a call to the underlying
+        stream's `async_read_some` method, with the resulting body
+        data stored in the referenced MutableBufferSequence.
+
+        All processing depends on a http_io::parser object owned
+        by the caller and referenced in the construction of this
+        object.
+
+        @see
+            @ref response_parser,
+            @ref request_parser.
+    */
+template<class AsyncReadStream>
+class body_read_stream {
+
+public:
+
+    /** The type of the executor associated with the stream.
+
+    This will be the type of executor used to invoke completion
+    handlers which do not have an explicit associated executor.
+    */
+    typedef AsyncReadStream::executor_type executor_type;
+
+    /** Get the executor associated with the object.
+
+    This function may be used to obtain the executor object that the
+    stream uses to dispatch completion handlers without an assocaited
+    executor.
+
+    @return A copy of the executor that stream will use to dispatch
+    handlers.
+    */
+    executor_type get_executor() {
+        return us_.get_executor();
+    }
+
+    /** Constructor
+
+    This constructor creates the stream by forwarding all arguments
+    to the underlying socket. The socket then needs to be open and
+    connected or accepted before data can be sent or received on it.
+
+    @param us The underlying stream from which the HTTP message is read.
+              This object's executor is initialized to that of the
+              underlying stream.
+
+    @param pr A http_proto::parser object which will perform the parsing
+              of the HTTP message and extraction of the body. This must
+              be initialized by the caller and ownership of the parser is
+              retained by the caller, which must guarantee that it remains
+              valid until the handler is called.
+    */
+    explicit
+        body_read_stream(
+            AsyncReadStream& us,
+            http_proto::parser& pr);
+
+    /** Read some data asynchronously.
+
+        This function is used to asynchronously read data from the stream.
+
+        This call always returns immediately. The asynchronous operation
+        will continue until one of the following conditions is true:
+
+        @li The HTTP headers are read in full from the underlying stream
+            and one or more bytes of the body are read from the stream and
+            stored in the buffer `mb`.
+
+        @li An error occurs.
+
+        The algorithm, known as a <em>composed asynchronous operation</em>,
+        is implemented in terms of calls to the underlying stream's `async_read_some`
+        function. The program must ensure that no other calls to @ref
+        `async_read_some` are performed until this operation completes.
+
+        @param mb The buffers into which the data will be read. If the size
+        of the buffers is zero bytes, the operation always completes immediately
+        with no error.
+        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 handler is called.
+        Where the mb buffer is not of sufficient size to hold the read data, the
+        remainder may be read by subsequent calls to this function.
+
+        @param handler The completion handler to invoke when the operation
+        completes. The implementation takes ownership of the handler by
+        performing a decay-copy. The equivalent function signature of
+        the handler must be:
+        @code
+        void handler(
+            error_code error,               // Result of operation.
+            std::size_t bytes_transferred   // Number of bytes read.
+        );
+        @endcode
+        If the handler has an associated immediate executor,
+        an immediate completion will be dispatched to it.
+        Otherwise, the handler will not be invoked from within
+        this function. Invocation of the handler will be performed
+        by dispatching to the immediate executor. If no
+        immediate executor is specified, this is equivalent
+        to using `net::post`.
+
+        @note The `async_read_some` operation may not receive all of the requested
+        number of bytes. Consider using the function `net::async_read` if you need
+        to ensure that the requested amount of data is read before the asynchronous
+        operation completes.
+
+        @par Per-Operation Cancellation
+
+        This asynchronous operation supports cancellation for the following
+        net::cancellation_type values:
+
+        @li @c net::cancellation_type::terminal
+        @li @c net::cancellation_type::partial
+        @li @c net::cancellation_type::total
+
+        if they are also supported by the underlying stream's @c async_read_some
+        operation.
+    */
+    template<
+        class MutableBufferSequence,
+        BOOST_ASIO_COMPLETION_TOKEN_FOR(
+            void(system::error_code, std::size_t)) CompletionToken>
+    BOOST_ASIO_INITFN_AUTO_RESULT_TYPE(CompletionToken,
+        void(system::error_code, std::size_t))
+    async_read_some(
+            const MutableBufferSequence& mb,
+            CompletionToken&& handler);
+
+    /** Read all remaining data asynchronously.
+        This function is used to asynchronously read data from the stream.
+
+        This call always returns immediately. The asynchronous operation
+        will continue until one of the following conditions is true:
+
+        @li The HTTP message is read in full from the underlying stream.
+
+        @li An error occurs.
+
+        The algorithm, known as a <em>composed asynchronous operation</em>,
+        is implemented in terms of calls to the underlying stream's `async_read_some`
+        function. The program must ensure that no other calls to @ref
+        `async_read_some` are performed until this operation completes.
+
+        @param mb The buffers into which the body data will be read. If the size
+        of the buffers is zero bytes, the operation always completes immediately
+        with no error.
+        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 handler is called.
+        Where the mb buffer is not of sufficient size to hold the read data, the
+        remainder may be read by subsequent calls to this function.
+
+        @param handler The completion handler to invoke when the operation
+        completes. The implementation takes ownership of the handler by
+        performing a decay-copy. The equivalent function signature of
+        the handler must be:
+        @code
+        void handler(
+            error_code error,               // Result of operation.
+            std::size_t bytes_transferred   // Number of bytes read.
+        );
+        @endcode
+        If the handler has an associated immediate executor,
+        an immediate completion will be dispatched to it.
+        Otherwise, the handler will not be invoked from within
+        this function. Invocation of the handler will be performed
+        by dispatching to the immediate executor. If no
+        immediate executor is specified, this is equivalent
+        to using `net::post`.
+
+        @note The `async_read_some` operation may not receive all of the requested
+        number of bytes. Consider using the function `net::async_read` if you need
+        to ensure that the requested amount of data is read before the asynchronous
+        operation completes.
+
+        @par Per-Operation Cancellation
+
+        This asynchronous operation supports cancellation for the following
+        net::cancellation_type values:
+
+        @li @c net::cancellation_type::terminal
+        @li @c net::cancellation_type::partial
+        @li @c net::cancellation_type::total
+
+        if they are also supported by the underlying stream's @c async_read_some
+        operation.
+    */
+    template<
+        class MutableBufferSequence,
+        BOOST_ASIO_COMPLETION_TOKEN_FOR(
+            void(system::error_code, std::size_t)) CompletionToken>
+    BOOST_ASIO_INITFN_AUTO_RESULT_TYPE(CompletionToken,
+        void(system::error_code, std::size_t))
+        async_read(
+            const MutableBufferSequence& mb,
+            CompletionToken&& handler);
+
+private:
+    AsyncReadStream& us_;
+    http_proto::parser& pr_;
+};
+
+} // beast2
+} // boost
+
+#include <boost/beast2/impl/body_read_stream.hpp>
+
+#endif