Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • docs
    • 2

    Description

      Update the docs on async/non blocking options for the 3.0 API, building upon https://docs.couchbase.com/c-sdk/2.10/async-programming.html

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            If my fix to the Batching include:: at https://docs.couchbase.com/c-sdk/current/howtos/concurrent-async-apis.html#batching works in tonight's docs build,
            this ticket could probably be closed.

            richard.smedley Richard Smedley added a comment - If my fix to the Batching include:: at https://docs.couchbase.com/c-sdk/current/howtos/concurrent-async-apis.html#batching works in tonight's docs build, this ticket could probably be closed.

            Richard Smedley While grooming, I can see that the batching contribution is a good addition. However, the original page referenced also includes a discussion on async IO that is more helpful than what we currently have. We do have a link to an example, but a description like we previously had would still be helpful to provide more information and context.

            ray.cardillo Ray Cardillo added a comment - Richard Smedley  While grooming, I can see that the batching contribution is a good addition. However, the original page referenced also includes a discussion on async IO that is more helpful than what we currently have. We do have a link to an example, but a description like we previously had would still be helpful to provide more information and context.

            Ray Cardillo I'd originally missed out the old async content, as it seemed unnecessary as default behaviour.

            How much of it would be useful to put back in? Anything that clears up understanding for the customers would be welcome.   

            richard.smedley Richard Smedley added a comment - Ray Cardillo  I'd originally missed out the old async content, as it seemed unnecessary as default behaviour. How much of it would be useful to put back in? Anything that clears up understanding for the customers would be welcome.   

            People

              avsej Sergey Avseyev
              richard.smedley Richard Smedley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty