<div dir="ltr"><div>Vijay,<br></div><div> nice catch, thanks.<br></div> <br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 19, 2013 at 2:29 PM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/17/2013 03:12 PM, Mingfan Lu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. use option is a good idea<br>
2. we could also traverse the this->children to see whether there is a<br>
xlator with type == protocol/client (depth first!)<br>
and save cache value in conf->use_with_client<br>
</blockquote>
<br>
Works for now. However, if new translators are introduced that actually perform chaining on the server side, this method will not be good enough. For e.g., a translator chain like this is possible<br>
<br>
<br>
Server1 Server2<br>
<br>
xlator<br>
|<br>
|<br>
|<br>
|<br>
protocol/client ------------------ protocol/server<br>
<br>
<br>
Work in progress translators like NSR[1] will possibly use such a scheme.<br>
<br>
-Vijay<br>
<br>
[1] <a href="https://forge.gluster.org/new-style-replication/nsr" target="_blank">https://forge.gluster.org/new-<u></u>style-replication/nsr</a><br>
</blockquote></div><br></div>