libcouchbase 0.0.1

data/ext/libcouchbase/CONTRIBUTING.md

@@ -0,0 +1,124 @@
+# Contributing
+
+In addition to filing bugs, you may contribute by submitting patches
+to fix bugs in the library. Contributions may be submitting to
+<http://review.couchbase.com>.  We use Gerrit as our code review system -
+and thus submitting a change would require an account there. Note that
+pull requests will not be ignored but will be responded to much quicker
+once they are converted into Gerrit.
+
+For something to be accepted into the codebase, it must be formatted
+properly and have undergone proper testing. While there are no formatting
+guidelines per se, the code should look similar to the existing code
+within the library.
+
+## Branches and Tags
+
+Released versions of the library are marked as annotated tags inside
+the repository.
+
+* The `release10` contains the older 1.x versions of the library.
+* The `release23` contains the current 2.3.x maintenance branch
+* The `master` branch represents the mainline branch. The master
+  branch typically consists of content going into the next release.
+
+## Contributing Patches
+
+If you wish to contribute a new feature or a bug fix to the library, try to follow
+the following guidelines to help ensure your change gets merged upstream.
+
+### Before you begin
+
+For any code change, ensure the new code you write looks similar to the code
+surrounding it. We have no strict code style policies, but do request that your
+code stand out as little as possible from its surrounding neighborhood (unless
+of course your change is stylistic in nature).
+
+If your change is going to involve a substantial amount of time or effort, please
+attempt to discuss it with the project developers first who will provide assistance
+and direction where possible.
+
+Additionally, note that the library uses C89 (AKA "ANSI C") with some extensions
+that are known to work on both GCC and Visual Studio. Please ensure your code
+conforms to this, unless the new code is specific to a given platform.
+
+#### For new features
+
+Ensure the feature you are adding does not already exist, and think about how
+this feature may be useful for other users. In general less intrusive changes
+are more likely to be accepted.
+
+#### For fixing bugs
+
+Ensure the bug you are fixing is actually a bug (and not a usage) error, and
+that it has not been fixed in a more recent version. Please read the release
+notes as well as the issue tracker to see a list of open and resolved issues.
+
+### Code Review
+
+#### Signing up on Gerrit
+
+Everything that is merged into the library goes through a code review process.
+The code review process is done via [Gerrit](http://review.couchbase.org)
+(Unfortunately we cannot merge pull requests, though it is fairly simple to
+convert a pull request to gerrit, as seen later. If you know a way to integrate
+pull requests with Gerrit, please let us know).
+
+To sign up for a gerrit account, go to http://review.couchbase.org and click
+on the _Register_ link at the top right. Once you've signed in you will need
+to sign the CLA (Contributor License Agreement) by going you your gerrit account
+page and selecting the _Agreements_ link on the left. When you've done that, be
+sure to notify us in IRC (at _#libcouchbase_) and/or send an email to
+**matt**AT**couchbase**DOTCOM as you will require manual approval before being
+able to submit a request for change.
+
+Once approved, you should add your public SSH key to gerrit.
+
+#### Setting up your fork with Gerrit
+
+Assuming you have a repository created like so:
+
+```
+$ git clone git://github.com/couchbase/libcouchbase.git
+```
+
+you can simply perform two simple steps to get started with gerrit:
+
+```
+$ git remote add gerrit ssh://${USERNAME}@review.couchbase.org:29418/libcouchbase
+$ scp -P 29418 ${USERNAME}@review.couchbase.org:hooks/commit-msg .git/hooks
+$ chmod a+x .git/hooks/commit-msg
+```
+
+The last change is required for annotating each commit message with a special
+header known as `Change-Id`. This allows Gerrit to group together different
+revisions of the same patch.
+
+#### Pushing a changeset
+
+Now that you have your change and a gerrit account to push to, you need to
+upload the change for review. To do so, invoke the following incantation:
+
+```
+$ git push gerrit HEAD:refs/for/master
+```
+
+Where `gerrit` is the name of the _remote_ added earlier. You may encounter
+some errors when pushing. The most common are:
+
+* "You are not authorized to push to this repository". You will get this if your
+  account has not yet been approved.
+* "Missing Change-Id". You need to install the `commit-msg` hook as described above.
+  Note that even once you do this, you will need to ensure that any prior commits
+  already have this header - this may be done by doing an interactive rebase (e.g.
+  `git rebase -i origin/master` and selecting `reword` for all the commits; which
+  will automatically fill in the Change-Id).
+
+
+Once you've pushed your changeset you can add people to review. Currently these
+are:
+
+* Mark Nunberg
+* Brett Lawson
+* Sergey Avseyev
+

data/ext/libcouchbase/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/ext/libcouchbase/README.markdown

@@ -0,0 +1,163 @@
+# Couchbase C Client
+
+[![Build Status](https://travis-ci.org/couchbase/libcouchbase.png?branch=master)](https://travis-ci.org/couchbase/libcouchbase)
+
+This is the C client library for [Couchbase](http://www.couchbase.com)
+It communicates with the cluster and speaks the relevant protocols
+necessary to connect to the cluster and execute data operations.
+
+## Features
+
+* Can function as either a synchronous or asynchronous library
+* Callback Oriented
+* Can integrate with most other asynchronous environments. You can write your
+  code to integrate it into your environment. Currently support exists for
+    * [libuv](http://github.com/joyent/libuv) (Windows and POSIX)
+    * [libev](http://software.schmorp.de/pkg/libev.html) (POSIX)
+    * [libevent](http://libevent.org/) (POSIX)
+    * `select` (Windows and POSIX)
+    * IOCP (Windows Only)
+* Support for operation batching
+* Cross Platform - Tested on Linux, OS X, and Windows.
+
+## Building
+
+Before you build from this repository, please check the
+[installation page](http://developer.couchbase.com/server/other-products/release-notes-archives/c-sdk)
+to see if there is a binary or release tarball available for your needs. Since the code here is
+not part of an official release it has therefore not gone through our
+release testing process.
+
+### Dependencies
+
+By default the library depends on:
+
+* _libevent_ (or _libev_) for the primary I/O backend.
+* _openssl_ for SSL transport.
+* _CMake_ version 2.8.9 or greater (for building)
+
+On Unix-like systems these dependencies are checked for by default
+while on Windows they are not checked by default.
+
+On Unix, the build system will expect to have _libevent_ or _libev_ installed,
+unless building plugins is explicitly disabled (see further).
+
+### Building on Unix-like systems
+
+Provided is a convenience script called `cmake/configure`. It is a Perl
+script and functions like a normal `autotools` script.
+
+```shell
+$ git clone git://github.com/couchbase/libcouchbase.git
+$ cd libcouchbase && mkdir build && cd build
+$ ../cmake/configure
+$ make
+$ ctest
+```
+
+### Building on Windows
+
+Assuming `git` and Visual Studio 2010 are installed, from a `CMD` shell, do:
+
+```
+C:\> git clone git://github.com/couchbase/libcouchbase.git
+C:\> mkdir lcb-build
+C:\> cd lcb-build
+C:\> cmake -G "Visual Studio 10" ..\libcouchbase
+C:\> cmake --build .
+```
+
+This will generate and build a Visual Studio `.sln` file.
+
+Windows builds are known to work on Visual Studio versions 2008, 2010 and
+2012.
+
+If you wish to link against OpenSSL, you should set the value of
+`OPENSSL_ROOT_DIR` to the location of the installation path, as described
+[here](https://github.com/Kitware/CMake/blob/master/Modules/FindOpenSSL.cmake)
+
+## Bugs, Support, Issues
+You may report issues in the library in our issue tracked at
+<http://couchbase.com/issues>. Sign up for an account and file an issue
+against the _Couchbase C Client Library_ project.
+
+The developers of the library hang out in IRC on `#libcouchbase` on
+irc.freenode.net.
+
+
+## Examples
+
+* The `examples` directory
+* Official client libraries using libcouchbase
+    * [node.js](http://github.com/couchbase/couchnode)
+    * [Python](http://github.com/couchbase/couchbase-python-client)
+    * [Ruby](http://github.com/couchbase/couchbase-ruby-client) (uses the old < 2.6 API)
+    * [PHP](http://github.com/couchbase/php-couchbase) (uses the old < 2.6 API)
+* Community projects using libcouchbase
+    * [C++11 wrapper](https://github.com/couchbaselabs/libcouchbase-cxx)
+    * [cberl - Couchbase NIF](https://github.com/chitika/cberl)
+    * [Perl client](https://github.com/mnunberg/perl-Couchbase-Client)
+
+## Documentation
+
+Documentation is available in guide format (introducing the basic concepts of
+Couchbase and the library). It is recommended for first-time users, and can
+be accessed at our [Documentation Site](http://developer.couchbase.com/documentation/server/4.5/sdk/c/start-using-sdk.html).
+
+API documentation is also available and is generated from the library's headers.
+It may contain references to more advanced features not found in the guide.
+
+API documentation may be generated by running `doxygen` within the source root
+directory. When this is done, you should have a `doc/html/index.html` page which
+may be viewed.
+
+Doxygen may be downloaded from the
+[doxygen downloads page](http://www.stack.nl/~dimitri/doxygen/download.html). Note
+however that most Linux distributions as well as Homebrew contain Doxygen in their
+repositories.
+
+```
+$ doxygen
+$ xdg-open doc/html/index.html # Linux
+$ open doc/html/index.html # OS X
+```
+
+You may also generate documentation using the `doc/Makefile` which dynamically
+inserts version information
+
+```
+$ make -f doc/Makefile public # for public documentation
+$ make -f doc/Makefile internal # for internal documentation
+```
+
+The generated documentation will be in the `doc/public/html` directory for
+public documentation, and in the `doc/internal/html` directory for internal
+documentation.
+
+## Contributors
+
+The following people contributed to libcouchbase (in alphabetic order)
+(last updated Nov. 27 2014)
+
+* Brett Lawson <brett19@gmail.com>
+* Dave Rigby <daver@couchbase.com>
+* Jan Lehnardt <jan@apache.org>
+* Mark Nunberg <mnunberg@haskalah.org>
+* Matt Ingenthron <ingenthr@cep.net>
+* Patrick Varley <patrick@couchbase.com>
+* Paul Farag <pfarag@neuraliq.com>
+* Pierre Joye <pierre.php@gmail.com>
+* Sebastian <sebastian@chango.com>
+* Sergey Avseyev <sergey.avseyev@gmail.com>
+* Subhashni Balakrishnan <b.subhashni@gmail.com>
+* Sundar Sridharan <sundar.sridharan@gmail.com>
+* Trond Norbye <trond.norbye@gmail.com>
+* Volker Mische <vmx@couchbase.com>
+* William Bowers <wbowers@neuraliq.com>
+* Yura Sokolov <funny.falcon@gmail.com>
+* Yury Alioshinov <haster2010@gmail.com>
+
+## License
+
+libcouchbase is licensed under the Apache 2.0 License. See `LICENSE` file for
+details.