Oh yes, I&#39;m still waiting on your prefeed solution to the &quot;isNil&quot; issue <br>
:-)<br>
<br>
Andy<br>
<br>
On Wed, 26 Jul 2017, Michael wrote:<br>
<br>
&gt; Yes, I am calling GetMetadata() from inside the ProcessResponse() callback.<br>
&gt;<br>
&gt; I had understood from the docs that there was a distinction between a metadata-only response and a data response with length zero, but I see now that there is no such distinction. From looking at the header files I see it is possible to detect a metadata-only response by inspecting the rInfo::mdlen and rInfo::blen member variables.<br>
&gt;<br>
&gt; The documentation should be updated to accurately describe this. The isNone enum value should be documented to make it clear that this value will never be seen in the callback.<br>
&gt;<br>
&gt; -- <br>
&gt; You are receiving this because you modified the open/close state.<br>
&gt; Reply to this email directly or view it on GitHub:<br>
&gt; https://github.com/xrootd/xrootd/issues/546#issuecomment-317967783<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/xrootd/xrootd/issues/546#issuecomment-317982911">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AD7Yji67GZfS5-UloRV0mQMtrJ1QTsltks5sRvX2gaJpZM4Od_re">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AD7YjoTUrU0jGMbTKaV2uLGyWtN3WJDyks5sRvX2gaJpZM4Od_re.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/xrootd/xrootd/issues/546#issuecomment-317982911"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<!cript type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@abh3 in #546: Oh yes, I'm still waiting on your prefeed solution to the \"isNil\" issue \n:-)\n\nAndy\n\nOn Wed, 26 Jul 2017, Michael wrote:\n\n\u003e Yes, I am calling GetMetadata() from inside the ProcessResponse() callback.\n\u003e\n\u003e I had understood from the docs that there was a distinction between a metadata-only response and a data response with length zero, but I see now that there is no such distinction. From looking at the header files I see it is possible to detect a metadata-only response by inspecting the rInfo::mdlen and rInfo::blen member variables.\n\u003e\n\u003e The documentation should be updated to accurately describe this. The isNone enum value should be documented to make it clear that this value will never be seen in the callback.\n\u003e\n\u003e -- \n\u003e You are receiving this because you modified the open/close state.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/546#issuecomment-317967783\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/546#issuecomment-317982911"}}}</script><br>
<hr>
<p align="left">
Use REPLY-ALL to reply to list</p>
<p align="center">To unsubscribe from the XROOTD-DEV list, click the following link:<br>
<a href="https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1" target="_blank">https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1</a>
</p>