RubyGems - couchbase - Versions diffs - 3.0.0.alpha.5 → 3.0.3 - Mend

couchbase 3.0.0.alpha.5 → 3.0.3

Files changed (1001) hide show

data/ext/third_party/asio/asio/src/doc/release_checklist.htm DELETED Viewed

@@ -1,68 +0,0 @@
-<html>
-  <head>
-    <title>asio Release Checklist</title>
-  </head>
-  <body>
-    <h1>asio Release Checklist</h1>
-    <form>
-      <table border="1">
-        <tr>
-          <td>Update version number in configure.ac</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Update version number and date in README</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Generate a clean distribution by doing a `make maintainer-clean`
-              followed by the steps necessary to do a `make dist'</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Unpack/build/test distribution on Mac OS X using g++ 4.0 with
-              adjacent boost directory</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Unpack/build/test distribution on Linux using g++ 3.4 using the
-              `--with-boost' configure option</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Unpack/build/test distribution on Solaris using g++ 3.3 with
-              adjacent boost directory</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Unpack/build/test distribution using MSVC 7.1 with adjacent boost
-              directory</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Unpack/build/test distribution using bcc32 5.6.4 with adjacent
-              boost directory</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Unpack/build/test distribution using MinGW-4.1.0 with adjacent
-              boost directory</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Commit version number changes to CVS</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Apply CVS tag of the form asio-x-y-z</td>
-          <td><input type="checkbox"></td>
-        </tr>
-        <tr>
-          <td>Generate a clean distribution by doing a `make maintainer-clean`
-              followed by the steps necessary to do a `make dist'</td>
-          <td><input type="checkbox"></td>
-        </tr>
-      </table>
-    </form>
-  </body>
-</html>

data/ext/third_party/asio/asio/src/doc/requirements/AcceptHandler.qbk DELETED Viewed

@@ -1,72 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:AcceptHandler Accept handler requirements]
-An accept handler must meet the requirements for a [link
-asio.reference.Handler handler]. A value `h` of an accept handler
-class should work correctly in the expression `h(ec)`, where `ec` is an lvalue
-of type `const error_code`.
-[heading Examples]
-A free function as an accept handler:
-  void accept_handler(
-      const asio::error_code& ec)
-  {
-    ...
-  }
-An accept handler function object:
-  struct accept_handler
-  {
-    ...
-    void operator()(
-        const asio::error_code& ec)
-    {
-      ...
-    }
-    ...
-  };
-A lambda as an accept handler:
-  acceptor.async_accept(...,
-      [](const asio::error_code& ec)
-      {
-        ...
-      });
-A non-static class member function adapted to an accept handler using
-`std::bind()`:
-  void my_class::accept_handler(
-      const asio::error_code& ec)
-  {
-    ...
-  }
-  ...
-  acceptor.async_accept(...,
-      std::bind(&my_class::accept_handler,
-        this, std::placeholders::_1));
-A non-static class member function adapted to an accept handler using
-`boost::bind()`:
-  void my_class::accept_handler(
-      const asio::error_code& ec)
-  {
-    ...
-  }
-  ...
-  acceptor.async_accept(...,
-      boost::bind(&my_class::accept_handler,
-        this, asio::placeholders::error));
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/AcceptableProtocol.qbk DELETED Viewed

@@ -1,25 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:AcceptableProtocol Acceptable protocol requirements]
-A type `X` meets the `AcceptableProtocol` requirements if it satisfies the
-requirements of [link asio.reference.Protocol `Protocol`] as well as the
-additional requirements listed below.
-[table AcceptableProtocol requirements
-  [[expression] [return type] [assertion/note[br]pre/post-conditions]]
-  [
-    [`X::socket`]
-    [A type that satisfies the requirements of `Destructible` (C++Std
-     \[destructible\]) and `MoveConstructible` (C++Std \[moveconstructible\]),
-     and that is publicly and unambiguously derived from `basic_socket<X>`.]
-    []
-  ]
-]
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/AsyncRandomAccessReadDevice.qbk DELETED Viewed

@@ -1,56 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:AsyncRandomAccessReadDevice Buffer-oriented asynchronous random-access
-read device requirements]
-In the table below, `a` denotes an asynchronous random access read device
-object, `o` denotes an offset of type `boost::uint64_t`, `mb` denotes an object
-satisfying [link asio.reference.MutableBufferSequence mutable buffer sequence]
-requirements, and `h` denotes an object satisfying [link
-asio.reference.ReadHandler read handler] requirements.
-[table Buffer-oriented asynchronous random-access read device requirements
-  [[operation] [type] [semantics, pre/post-conditions]]
-  [
-    [`a.get_executor()`]
-    [A type satisfying the [link asio.reference.Executor1 Executor requirements].]
-    [Returns the associated I/O executor.]
-  ]
-  [
-    [`a.async_read_some_at(o, mb, h);`]
-    [`void`]
-    [
-      Initiates an asynchronous operation to read one or more bytes of data
-      from the device `a` at the offset `o`. The operation is performed via the
-      `io_service` object `a.get_io_service()` and behaves according to [link
-      asio.reference.asynchronous_operations asynchronous operation]
-      requirements.[br]
-      [br]
-      The mutable buffer sequence `mb` specifies memory where the data should
-      be placed. The `async_read_some_at` operation shall always fill a buffer
-      in the sequence completely before proceeding to the next.[br]
-      [br]
-      The implementation shall maintain one or more copies of `mb` until such
-      time as the read operation no longer requires access to the memory
-      specified by the buffers in the sequence. The program must ensure the
-      memory is valid until:[br]
-      [br]
-      [mdash] the last copy of `mb` is destroyed, or[br]
-      [br]
-      [mdash] the handler for the asynchronous read operation is invoked,[br]
-      [br]
-      whichever comes first.[br]
-      [br]
-      If the total size of all buffers in the sequence `mb` is `0`, the
-      asynchronous read operation shall complete immediately and pass `0` as
-      the argument to the handler that specifies the number of bytes read.
-    ]
-  ]
-]
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/AsyncRandomAccessWriteDevice.qbk DELETED Viewed

@@ -1,57 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:AsyncRandomAccessWriteDevice Buffer-oriented asynchronous
-random-access write device requirements]
-In the table below, `a` denotes an asynchronous write stream object, `o`
-denotes an offset of type `boost::uint64_t`, `cb` denotes an object satisfying
-[link asio.reference.ConstBufferSequence constant buffer sequence]
-requirements, and `h` denotes an object satisfying [link
-asio.reference.WriteHandler write handler] requirements.
-[table Buffer-oriented asynchronous random-access write device requirements
-  [[operation] [type] [semantics, pre/post-conditions]]
-  [
-    [`a.get_executor()`]
-    [A type satisfying the [link asio.reference.Executor1 Executor requirements].]
-    [Returns the associated I/O executor.]
-  ]
-  [
-    [`a.async_write_some_at(o, cb, h);`]
-    [`void`]
-    [
-      Initiates an asynchronous operation to write one or more bytes of data to
-      the device `a` at offset `o`. The operation is performed via the
-      `io_service` object `a.get_io_service()` and behaves according to [link
-      asio.reference.asynchronous_operations asynchronous operation]
-      requirements.[br]
-      [br]
-      The constant buffer sequence `cb` specifies memory where the data to be
-      written is located. The `async_write_some_at` operation shall always
-      write a buffer in the sequence completely before proceeding to the
-      next.[br]
-      [br]
-      The implementation shall maintain one or more copies of `cb` until such
-      time as the write operation no longer requires access to the memory
-      specified by the buffers in the sequence. The program must ensure the
-      memory is valid until:[br]
-      [br]
-      [mdash] the last copy of `cb` is destroyed, or[br]
-      [br]
-      [mdash] the handler for the asynchronous write operation is invoked,[br]
-      [br]
-      whichever comes first.[br]
-      [br]
-      If the total size of all buffers in the sequence `cb` is `0`, the
-      asynchronous write operation shall complete immediately and pass `0` as
-      the argument to the handler that specifies the number of bytes written.
-    ]
-  ]
-]
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/AsyncReadStream.qbk DELETED Viewed

@@ -1,50 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:AsyncReadStream Buffer-oriented asynchronous read stream requirements]
-A type `X` meets the `AsyncReadStream` requirements if it satisfies the
-requirements listed below.
-In the table below, `a` denotes a value of type `X`, `mb` denotes a (possibly
-const) value satisfying the [link asio.reference.MutableBufferSequence
-`MutableBufferSequence`] requirements, and `t` is a completion token.
-[table AsyncReadStream requirements
-  [[operation] [type] [semantics, pre/post-conditions]]
-  [
-    [`a.get_executor()`]
-    [A type satisfying the [link asio.reference.Executor1 Executor requirements].]
-    [Returns the associated I/O executor.]
-  ]
-  [
-    [`a.async_read_some(mb,t)`]
-    [
-      The return type is determined according to the requirements for an
-      [link asio.reference.asynchronous_operations asynchronous operation].
-    ]
-    [
-      Meets the requirements for a [link asio.reference.read_write_operations
-      read operation] and an [link asio.reference.asynchronous_operations
-      asynchronous operation] with completion signature `void(error_code ec,
-      size_t n)`.[br]
-      [br]
-      If `buffer_size(mb) > 0`, initiates an asynchronous operation to read one
-      or more bytes of data from the stream `a` into the buffer sequence `mb`.
-      If successful, `ec` is set such that `!ec` is `true`, and `n` is the
-      number of bytes read. If an error occurred, `ec` is set such that `!!ec`
-      is `true`, and `n` is 0. If all data has been read from the stream, and
-      the stream performed an orderly shutdown, `ec` is
-      `stream_errc::eof` and `n` is 0.[br]
-      [br]
-      If `buffer_size(mb) == 0`, the operation completes immediately. `ec` is
-      set such that `!ec` is `true`, and `n` is 0.
-    ]
-  ]
-]
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/AsyncWriteStream.qbk DELETED Viewed

@@ -1,48 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:AsyncWriteStream Buffer-oriented asynchronous write stream requirements]
-A type `X` meets the `AsyncWriteStream` requirements if it satisfies the
-requirements listed below.
-In the table below, `a` denotes a value of type `X`, `cb` denotes a (possibly
-const) value satisfying the [link asio.reference.ConstBufferSequence
-`ConstBufferSequence`] requirements, and `t` is a completion token.
-[table AsyncWriteStream requirements
-  [[operation] [type] [semantics, pre/post-conditions]]
-  [
-    [`a.get_executor()`]
-    [A type satisfying the [link asio.reference.Executor1 Executor requirements].]
-    [Returns the associated I/O executor.]
-  ]
-  [
-    [`a.async_write_some(cb,t)`]
-    [
-      The return type is determined according to the requirements for an
-      [link asio.reference.asynchronous_operations asynchronous operation].
-    ]
-    [
-      Meets the requirements for a [link asio.reference.read_write_operations
-      write operation] and an [link asio.reference.asynchronous_operations
-      asynchronous operation] with completion signature `void(error_code ec,
-      size_t n)`.[br]
-      [br]
-      If `buffer_size(cb) > 0`, initiates an asynchronous operation to write
-      one or more bytes of data to the stream `a` from the buffer sequence
-      `cb`. If successful, `ec` is set such that `!ec` is `true`, and `n` is
-      the number of bytes written. If an error occurred, `ec` is set such that
-      `!!ec` is `true`, and `n` is 0.[br]
-      [br]
-      If `buffer_size(cb) == 0`, the operation completes immediately. `ec` is
-      set such that `!ec` is `true`, and `n` is 0.
-    ]
-  ]
-]
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/BufferedHandshakeHandler.qbk DELETED Viewed

@@ -1,55 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:BufferedHandshakeHandler Buffered handshake handler requirements]
-A buffered handshake handler must meet the requirements for a [link
-asio.reference.Handler handler]. A value `h` of a buffered handshake handler
-class should work correctly in the expression `h(ec, s)`, where `ec` is an
-lvalue of type `const error_code` and `s` is an lvalue of type `const size_t`.
-[heading Examples]
-A free function as a buffered handshake handler:
-  void handshake_handler(
-      const asio::error_code& ec,
-      std::size_t bytes_transferred)
-  {
-    ...
-  }
-A buffered handshake handler function object:
-  struct handshake_handler
-  {
-    ...
-    void operator()(
-        const asio::error_code& ec,
-        std::size_t bytes_transferred)
-    {
-      ...
-    }
-    ...
-  };
-A non-static class member function adapted to a buffered handshake handler
-using `boost::bind()`:
-  void my_class::handshake_handler(
-      const asio::error_code& ec,
-      std::size_t bytes_transferred)
-  {
-    ...
-  }
-  ...
-  socket.async_handshake(...,
-      boost::bind(&my_class::handshake_handler,
-        this, asio::placeholders::error,
-        asio::placeholders::bytes_transferred));
-[endsect]

data/ext/third_party/asio/asio/src/doc/requirements/CompletionCondition.qbk DELETED Viewed

@@ -1,42 +0,0 @@
-[/
- / Copyright (c) 2003-2020 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)
- /]
-[section:CompletionCondition Completion condition requirements]
-A ['completion condition] is a function object that is used with the algorithms
-[link asio.reference.read `read`], [link asio.reference.async_read
-`async_read`], [link asio.reference.write `write`], and [link
-asio.reference.async_write `async_write`] to determine when the algorithm has
-completed transferring data.
-A type `X` meets the `CompletionCondition` requirements if it satisfies the
-requirements of `Destructible` (C++Std [destructible]) and
-`MoveConstructible` (C++Std [moveconstructible]), as well as the additional
-requirements listed below.
-In the table below, `x` denotes a value of type `X`, `ec` denotes a (possibly
-const) value of type `error_code`, and `n` denotes a (possibly const) value of
-type `size_t`.
-[table CompletionCondition requirements
-  [[expression] [return type] [assertion/note[br]pre/post-condition]]
-  [
-    [`x(ec, n)`]
-    [`size_t`]
-    [
-      Let `n` be the total number of bytes transferred by the read or write
-      algorithm so far.[br]
-      [br]
-      Returns the maximum number of bytes to be transferred on the next
-      `read_some`, `async_read_some`, `write_some`, or `async_write_some`
-      operation performed by the algorithm. Returns `0` to indicate that the
-      algorithm is complete.
-    ]
-  ]
-]
-[endsect]