[dotNetRDF-Develop] Issue CORE-423 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>SparqlJsonParser fails to parse results of ASK queries with atypical ordering</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2014-07-04 11:15 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	The specific case and some related cases have been fixed.</p>
<p>
	Please note that our parser is designed to be streaming so it is unlikely to ever cope with every possible unusual variation of the SPARQL Results JSON. &nbsp;In principal we could in the future add a DOM based parser that would not attempt to stream the data rather it would load the whole JSON document into memory up-front. &nbsp;That obviously makes a trade off in terms of memory usage and likely leads to an inability to cope with really large result sets which is something we&#39;ve seen with our XML based parsers in the past. &nbsp;While the overhead of a JSON DOM is likely much lower than that of an XML DOM the issue would still exist.</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=423" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=423</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>