<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed May 22 00:32:02 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/NCBC-78/NCBC-78.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[NCBC-78] Enhance discussion of return codes/values</title>
                <link>http://www.couchbase.com/issues/browse/NCBC-78</link>
                <project id="10046" key="NCBC">Couchbase .NET client library</project>
                        <description>Given the comments on this page: &lt;a href=&quot;http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html&quot;&gt;http://www.couchbase.com/docs/couchbase-sdk-net-1.1/couchbase-sdk-net-retrieve-set.html&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
Perhaps there can be a section on the possible return codes/values, what they mean, when they might happen, and how to deal with them?</description>
                <environment></environment>
            <key id="18027">NCBC-78</key>
            <summary>Enhance discussion of return codes/values</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="1" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="john">John Zablocki</assignee>
                                <reporter username="perry">Perry Krug</reporter>
                        <labels>
                    </labels>
                <created>Tue, 26 Jun 2012 09:31:05 -0500</created>
                <updated>Fri, 7 Dec 2012 21:41:33 -0600</updated>
                                    <version>1.1.6</version>
                                <fixVersion>1.3</fixVersion>
                                <component>docs</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="44681" author="mnunberg" created="Thu, 22 Nov 2012 20:26:31 -0600"  >This is a must-have for SDK testing. It is very difficult to determine failure types and severities without knowing what types of errors, exception classes, or such to expect.&lt;br/&gt;
&lt;br/&gt;
At the very least, there should be standard return codes (in a well-defined location) for memcached error codes.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>9993</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>