<div dir="ltr">Hi Niels,<div><br></div><div>I guess these are the related issues you were looking for:</div><div><a href="https://github.com/gluster/glusterfs/issues/203">https://github.com/gluster/glusterfs/issues/203</a><br></div><div><a href="https://github.com/gluster/glusterfs/issues/67">https://github.com/gluster/glusterfs/issues/67</a><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 11, 2017 at 6:41 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Aug 11, 2017 at 06:04:36PM +0530, Amar Tumballi wrote:<br>
> Hi All,<br>
><br>
> Below are the proposed protocol changes (ie, XDR changes on the wire) we<br>
> are thinking for Gluster 4.0.<br>
<br>
</span>One of the things that is missing in this list, is to have dictionary<br>
entries have a (key, type, value) format. This makes it possible to have<br>
all the values XDR encoded/decoded correctly. When new values get<br>
transported over the network, we can force the need for XDR encoding<br>
functions for these types.<br>
<br>
I thought there was a GitHub issue for this already (or maybe a bug?),<br>
but I fail to find it.<br>
<br>
Niels<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div>