From: Dan Mick <dan.mick@inktank.com>
To: Noah Watkins <noah.watkins@inktank.com>
Cc: Niklas Goerke <niklas@niklasgoerke.de>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Rados Protocoll
Date: Mon, 05 Aug 2013 20:16:48 -0700 [thread overview]
Message-ID: <52006AA0.1090604@inktank.com> (raw)
In-Reply-To: <CA+Hcz58ROZ5Ea36YK6-n4Gz=L8wvQ9EWo4j-OiMwY_j_FPvjJg@mail.gmail.com>
On 08/04/2013 10:51 PM, Noah Watkins wrote:
> On Fri, Aug 2, 2013 at 1:58 AM, Niklas Goerke <niklas@niklasgoerke.de> wrote:
>>
>> As for the documentation you referenced: I didn't find a documentation of
>> the RADOS Protocol which could be used to base an implementation of librados
>> upon. Does anything like this exist, or would I need to "translate" the c
>> implementation?
>
> I do not know of any detailed documentation of the protocol except for
> the source :(
...nor, it should be pointed out, is it to be considered at all stable...
prev parent reply other threads:[~2013-08-06 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 20:01 Rados Protocoll Niklas Goerke
2013-08-01 21:53 ` Noah Watkins
2013-08-02 8:58 ` Niklas Goerke
2013-08-05 5:51 ` Noah Watkins
2013-08-06 3:16 ` Dan Mick [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52006AA0.1090604@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=niklas@niklasgoerke.de \
--cc=noah.watkins@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.